[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH v3] xen: introduce VCPUOP_register_runstate_phys_memory_area hypercall
- To: <andrii.anisov@xxxxxxxxx>
- From: "Jan Beulich" <JBeulich@xxxxxxxx>
- Date: Mon, 17 Jun 2019 00:27:47 -0600
- Cc: Stefano Stabellini <sstabellini@xxxxxxxxxx>, Wei Liu <wei.liu2@xxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Tim Deegan <tim@xxxxxxx>, Julien Grall <julien.grall@xxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, "andrii_anisov@xxxxxxxx" <andrii_anisov@xxxxxxxx>, Roger Pau Monne <roger.pau@xxxxxxxxxx>
- Delivery-date: Mon, 17 Jun 2019 06:28:03 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
>>> On 14.06.19 at 18:25, <andrii.anisov@xxxxxxxxx> wrote:
> On 14.06.19 19:20, Julien Grall wrote:
>> Well, that a stable ABI... Even if I would love to remove it, you can't get
> rid of old guests that easily...
>
> In 5 years, as XEN did for LK 3.18?
I'm afraid I don't even know how to best word a reply to this. What
has the Linux kernel version got to do with the interfaces provided
by Xen? Is your reply meant to say that something was removed
from the Linux kernel in that version? That's fine - consumers can
stop consuming interfaces they don't like to use. But Xen (the
producer of interfaces like the one discussed here) can't lightly stop
providing interfaces, irrespective of their use in upstream Linux.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel
|
