xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Tim Deegan <tim@xen.org>, Paul Durrant <paul.durrant@citrix.com>,
	David Vrabel <david.vrabel@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: HVMlite ABI specification DRAFT B + implementation outline
Date: Wed, 10 Feb 2016 15:51:44 +0100	[thread overview]
Message-ID: <56BB4E80.6070800@citrix.com> (raw)
In-Reply-To: <56BB40D302000078000D0899@prv-mh.provo.novell.com>

El 10/2/16 a les 13:53, Jan Beulich ha escrit:
>>>> On 10.02.16 at 13:01, <roger.pau@citrix.com> wrote:
>> El 9/2/16 a les 14:24, Jan Beulich ha escrit:
>>>>>> On 08.02.16 at 20:03, <roger.pau@citrix.com> wrote:
>>>>  * 2. HVMlite with (or capable to) PCI-passthrough
>>>>    -----------------------------------------------
>>>>    The current model of PCI-passthrought in PV guests is complex and requires
>>>>    heavy modifications to the guest OS. Going forward we would like to remove
>>>>    this limitation, by providing an interface that's the same as found on bare
>>>>    metal. In order to do this, at least an emulated local APIC should be
>>>>    provided to guests, together with the access to a PCI-Root complex.
>>>>    As said in the 'Hardware description' section above, this will also require
>>>>    ACPI. So this proposed scenario will require the following elements that are
>>>>    not present in the minimal (or default) HVMlite implementation: ACPI, local
>>>>    APIC, IO APIC (optional) and PCI-Root complex.
>>>
>>> Are you reasonably convinced that the absence of an IO-APIC
>>> won't, with LAPICs present, cause more confusion than aid to the
>>> OSes wanting to adopt PVHv2?
>>
>> As long as the data provided in the MADT represent the container
>> provided I think we should be fine. In the case of no IO APICs no
>> entries of type 1 (IO APIC) will be provided in the MADT.
> 
> I understand that, but are certain OSes are prepared for that?

Well, given that some modifications will always be needed in order to
run as a PVH guest, I don't think this should stop us. FWIW, I think
FreeBSD should be able to cope with this without much fuss:

https://svnweb.freebsd.org/base/head/sys/x86/acpica/madt.c?revision=291686&view=co

The detection of local APIC and IO APICs is quite isolated from each
other, and the failure to find any IO APICs should not prevent local
APICs from being enabled. Although I don't think there's any hardware
with this setup, such configuration would be valid from an ACPI point of
view. I've of course not tested this in any way, so those are only
observations by a quick look at the code. I cannot speak about Linux.

Also, thanks for the observations and comments on the document.

Roger.

  reply	other threads:[~2016-02-10 14:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 19:03 HVMlite ABI specification DRAFT B + implementation outline Roger Pau Monné
2016-02-08 21:26 ` Boris Ostrovsky
2016-02-09 10:56 ` Andrew Cooper
2016-02-09 11:58   ` Roger Pau Monné
2016-02-09 12:10     ` Jan Beulich
2016-02-09 13:00       ` Roger Pau Monné
2016-02-09 13:41         ` Jan Beulich
2016-02-09 16:32           ` Roger Pau Monné
2016-02-09 16:41             ` Jan Beulich
2016-02-09 14:36     ` Boris Ostrovsky
2016-02-09 14:42       ` Andrew Cooper
2016-02-09 14:48       ` Jan Beulich
2016-02-09 13:24 ` Jan Beulich
2016-02-09 15:06   ` Stefano Stabellini
2016-02-09 16:15     ` Jan Beulich
2016-02-09 16:17       ` David Vrabel
2016-02-09 16:28         ` Jan Beulich
2016-02-09 16:26       ` Stefano Stabellini
2016-02-09 16:33         ` Jan Beulich
2016-02-10 12:01   ` Roger Pau Monné
2016-02-10 12:53     ` Jan Beulich
2016-02-10 14:51       ` Roger Pau Monné [this message]
2016-02-10 15:14         ` Boris Ostrovsky
2016-02-09 15:14 ` Boris Ostrovsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56BB4E80.6070800@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=paul.durrant@citrix.com \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).