From: Boris Ostrovsky <email@example.com> To: Jan Beulich <JBeulich@suse.com> Cc: Andrew Cooper <firstname.lastname@example.org>, xen-devel <email@example.com> Subject: Re: [PATCH 2/2] hvmloader: don't hard-code IO-APIC parameters Date: Fri, 17 Jun 2016 07:51:20 -0400 [thread overview] Message-ID: <5763E438.firstname.lastname@example.org> (raw) In-Reply-To: <5763AE1302000078000F5E2F@prv-mh.provo.novell.com> On 06/17/2016 02:00 AM, Jan Beulich wrote: >>>> On 16.06.16 at 18:49, <email@example.com> wrote: >> 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? > If this refers to the sentence in parentheses, then this was really > meant to indicate a work item. I.e. qemu should negotiate with > Xen. For PVHv2 this would then probably mean for hvmloader to > query Xen (via new hypercall). We are not using hvmloader for PVH so I am not sure how that would work. You mean the toolstack? -boris _______________________________________________ Xen-devel mailing list Xenfirstname.lastname@example.org http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-17 11:51 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 2016-06-17 6:00 ` Jan Beulich 2016-06-17 11:51 ` Boris Ostrovsky [this message] 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: 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=5763E438.email@example.com \ --firstname.lastname@example.org \ --cc=JBeulich@suse.com \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 2/2] hvmloader: don'\''t hard-code IO-APIC parameters' \ /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
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).