From: David Vrabel <david.vrabel@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] xen, apic: Setup our own APIC driver and validator for APIC IDs.
Date: Mon, 2 Mar 2015 17:25:55 +0000 [thread overview]
Message-ID: <54F49D23.40200@citrix.com> (raw)
In-Reply-To: <20150302170623.GN3418@l.oracle.com>
On 02/03/15 17:06, Konrad Rzeszutek Wilk wrote:
> Subject: [PATCH] x86/xen: Provide a "Xen PV" APIC driver to support >255 VCPUs
>
> Instead of mangling the default APIC driver, provide a Xen PV guest
> specific one that explicitly provides appropriate methods.
>
> This allows use to report that all APIC IDs are valid, allowing dom0
> to boot with more than 255 VCPUs.
>
> Since the probe order of APIC drivers is link dependent, we add in an
> late probe function to change to the Xen PV if it hadn't been done
> during bootup.
Applied to devel/for-linus-4.1, thanks.
I've only given the briefest of smoke-tests. It would probably be a
good idea to queue this branch for some testing early.
David
next prev parent reply other threads:[~2015-03-02 17:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 21:14 [PATCH] xen,apic: Setup our own APIC driver and validator for APIC IDs Konrad Rzeszutek Wilk
2015-03-02 11:24 ` [PATCH] xen, apic: " David Vrabel
2015-03-02 11:24 ` [Xen-devel] " David Vrabel
2015-03-02 14:22 ` Konrad Rzeszutek Wilk
2015-03-02 14:22 ` [Xen-devel] " Konrad Rzeszutek Wilk
[not found] ` <54F47646.1070707@citrix.com>
2015-03-02 17:06 ` Konrad Rzeszutek Wilk
2015-03-02 17:25 ` David Vrabel [this message]
2015-03-02 17:32 ` Konrad Rzeszutek Wilk
2015-03-02 17:34 ` Boris Ostrovsky
-- strict thread matches above, loose matches on Subject: below --
2015-02-27 21:14 Konrad Rzeszutek Wilk
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=54F49D23.40200@citrix.com \
--to=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.