xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [PATCH 2/2] hvmloader: don't hard-code IO-APIC parameters
Date: Thu, 16 Jun 2016 12:49:43 -0400	[thread overview]
Message-ID: <5762D8A7.3010205@oracle.com> (raw)
In-Reply-To: <5762903B02000078000F597E@prv-mh.provo.novell.com>

On 06/16/2016 05:40 AM, Jan Beulich wrote:
> The IO-APIC address has variable bits determined by the PCI-to-ISA
> bridge, and the IO-APIC version should be read from the IO-APIC. (Note
> that there's still implicit rather than explicit agreement on the
> IO-APIC base address between qemu and the hypervisor.)

It probably doesn't matter now for PVHv2 since we are not going to
initially emulate IOAPIC but when/if we do, how do we query for base
address and version? Should we just rely on the same implicit agreement?


Xen-devel mailing list

  reply	other threads:[~2016-06-16 16:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-16  9:33 [PATCH 0/2] x86: hvmloader improvements Jan Beulich
2016-06-16  9:40 ` [PATCH 1/2] hvmloader: limit CPUs exposed to guests Jan Beulich
2016-06-16 15:09   ` Boris Ostrovsky
2016-06-16 15:25     ` Jan Beulich
2016-06-16 15:37       ` Boris Ostrovsky
2016-06-16 16:04         ` Jan Beulich
2016-06-16 16:38           ` Boris Ostrovsky
2016-06-17  9:40   ` Andrew Cooper
2016-06-16  9:40 ` [PATCH 2/2] hvmloader: don't hard-code IO-APIC parameters Jan Beulich
2016-06-16 16:49   ` Boris Ostrovsky [this message]
2016-06-17  6:00     ` Jan Beulich
2016-06-17 11:51       ` Boris Ostrovsky
2016-06-17 14:26         ` Jan Beulich
2016-06-17 10:05   ` Andrew Cooper
2016-06-17 10:23     ` Jan Beulich

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:

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

  git send-email \
    --in-reply-to=5762D8A7.3010205@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xenproject.org \


* 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).