[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [Qemu-devel] [RFC QEMU PATCH v3 00/10] Implement vNVDIMM for Xen HVM guest
- To: "Haozhong Zhang" <haozhong.zhang@xxxxxxxxx>
- From: "Jan Beulich" <JBeulich@xxxxxxxx>
- Date: Fri, 13 Oct 2017 06:13:10 -0600
- Cc: Stefano Stabellini <sstabellini@xxxxxxxxxx>, wei.liu2@xxxxxxxxxx, Xiao Guangrong <xiaoguangrong.eric@xxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, qemu-devel@xxxxxxxxxx, andrew.cooper3@xxxxxxxxxx, "Michael S. Tsirkin" <mst@xxxxxxxxxx>, ian.jackson@xxxxxxxxxxxxx, george.dunlap@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxx, Igor Mammedov <imammedo@xxxxxxxxxx>, Paolo Bonzini <pbonzini@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, Anthony Perard <anthony.perard@xxxxxxxxxx>, Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>, Dan Williams <dan.j.williams@xxxxxxxxx>, Richard Henderson <rth@xxxxxxxxxxx>, Eduardo Habkost <ehabkost@xxxxxxxxxx>
- Delivery-date: Fri, 13 Oct 2017 12:13:22 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
>>> On 13.10.17 at 13:13, <haozhong.zhang@xxxxxxxxx> wrote:
> To Jan, Andrew, Stefano and Anthony,
>
> what do you think about allowing QEMU to build the entire guest ACPI
> and letting SeaBIOS to load it? ACPI builder code in hvmloader is
> still there and just bypassed in this case.
Well, if that can be made work in a non-quirky way and without
loss of functionality, I'd probably be fine. I do think, however,
that there's a reason this is being handled in hvmloader right now.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel
|
