[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH v2 2/3] x86/ioreq server: Rename p2m_mmio_write_dm to p2m_ioreq_server
- To: Jan Beulich <jbeulich@xxxxxxxx>
- From: George Dunlap <george.dunlap@xxxxxxxxxx>
- Date: Wed, 20 Apr 2016 18:08:54 +0100
- Cc: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, Keir Fraser <keir@xxxxxxx>, Andrew Cooper <Andrew.Cooper3@xxxxxxxxxx>, Tim Deegan <tim@xxxxxxx>, "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>, Paul Durrant <Paul.Durrant@xxxxxxxxxx>, "Yu, Zhang" <yu.c.zhang@xxxxxxxxxxxxxxx>, "Lv, Zhiyuan" <zhiyuan.lv@xxxxxxxxx>, Jun Nakajima <jun.nakajima@xxxxxxxxx>, Wei Liu <wei.liu2@xxxxxxxxxx>
- Delivery-date: Wed, 20 Apr 2016 17:09:08 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On Wed, Apr 20, 2016 at 5:52 PM, Jan Beulich <jbeulich@xxxxxxxx> wrote:
>>If it's the case that the only code that uses this is in XenServer,
>>then I'd say the answer to #1 can be simply, "Don't compile" and
>>"Don't do that" respectively; and the answer to #2 can be either
>>"Leave it be" or "Remove the enum from the public interface".
>>
>>If there are other projects that have started to use this interface,
>>then we need a better answer to #1 than "Compile but fail in
>>unpredicatble ways".
>
> How would we know whether there are other users?
Well we'd wait for them to complain... at which point we would have
had a release with an *incompatible* ABI and no way to change it.
So yes, upon consideration, burning the enum value is really the only
option. :-)
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
