[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 1/7] iohandlers: Mark current implementation as
From: |
Amit Shah |
Subject: |
Re: [Qemu-devel] [PATCH 1/7] iohandlers: Mark current implementation as 'old' |
Date: |
Tue, 22 Feb 2011 20:07:26 +0530 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On (Tue) 22 Feb 2011 [15:28:59], Avi Kivity wrote:
> On 02/22/2011 01:17 PM, Amit Shah wrote:
> >On (Tue) 22 Feb 2011 [13:09:34], Avi Kivity wrote:
> >> On 02/22/2011 12:18 PM, Amit Shah wrote:
> >> >Mark the current iohandler list as 'old'. In the next commit we'll
> >> >introduce a new iohandler api that will replace the list name.
> >> >
> >> >The 'old' list will eventually be completely replaced by the new
> >> >implementation.
> >>
> >> A better way to do this is to implement the old API in terms of the
> >> new API. This ensures you don't lose any functionality, and reduces
> >> the amount of low-level infrastructure.
> >
> >With this new approach of switching to just one callback, that is more
> >work for little gain as we'll just deprecate the older API soon. (The
> >previous patches used this approach, btw.)
>
> Does "deprecate" mean "completely remove"?
>
> If so I agree.
Yes, completely removing the older API is the plan (as noted in
message 00).
Amit
[Qemu-devel] [PATCH 2/7] iohandlers: Introduce a new API, Amit Shah, 2011/02/22
- Re: [Qemu-devel] [PATCH 2/7] iohandlers: Introduce a new API, Alon Levy, 2011/02/22
- Re: [Qemu-devel] [PATCH 2/7] iohandlers: Introduce a new API, Avi Kivity, 2011/02/22
- Re: [Qemu-devel] [PATCH 2/7] iohandlers: Introduce a new API, Amit Shah, 2011/02/22
- Re: [Qemu-devel] [PATCH 2/7] iohandlers: Introduce a new API, Anthony Liguori, 2011/02/22
- Re: [Qemu-devel] [PATCH 2/7] iohandlers: Introduce a new API, Avi Kivity, 2011/02/22
- Re: [Qemu-devel] [PATCH 2/7] iohandlers: Introduce a new API, Anthony Liguori, 2011/02/22
- Re: [Qemu-devel] [PATCH 2/7] iohandlers: Introduce a new API, Avi Kivity, 2011/02/23