From: Paolo Bonzini <pbonzini@redhat.com>
To: Lan Tianyu <tianyu.lan@intel.com>, qemu-devel@nongnu.org
Cc: mst@redhat.com, rth@twiddle.net, ehabkost@redhat.com,
anthony.perard@citrix.com, xen-devel@lists.xenproject.org
Subject: Re: [Qemu-devel] [PATCH] x86: Skip check apic_id_limit for Xen
Date: Wed, 16 Aug 2017 13:21:37 +0200 [thread overview]
Message-ID: <34042934-782b-6bcc-b9b2-de7a1816cfb7@redhat.com> (raw)
In-Reply-To: <1502842933-8323-1-git-send-email-tianyu.lan@intel.com>
On 16/08/2017 02:22, Lan Tianyu wrote:
> Xen vIOMMU device model will be in Xen hypervisor. Skip vIOMMU
> check for Xen here when vcpu number is more than 255.
I think you still need to do a check for vIOMMU being enabled.
Paolo
> Signed-off-by: Lan Tianyu <tianyu.lan@intel.com>
> ---
> hw/i386/pc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/i386/pc.c b/hw/i386/pc.c
> index 5943539..fc17885 100644
> --- a/hw/i386/pc.c
> +++ b/hw/i386/pc.c
> @@ -1260,7 +1260,7 @@ void pc_machine_done(Notifier *notifier, void *data)
> fw_cfg_modify_i16(pcms->fw_cfg, FW_CFG_NB_CPUS, pcms->boot_cpus);
> }
>
> - if (pcms->apic_id_limit > 255) {
> + if (pcms->apic_id_limit > 255 && !xen_enabled()) {
> IntelIOMMUState *iommu = INTEL_IOMMU_DEVICE(x86_iommu_get_default());
>
> if (!iommu || !iommu->x86_iommu.intr_supported ||
>
next prev parent reply other threads:[~2017-08-16 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 0:22 [Qemu-devel] [PATCH] x86: Skip check apic_id_limit for Xen Lan Tianyu
2017-08-16 11:21 ` Paolo Bonzini [this message]
2017-08-17 1:37 ` Lan Tianyu
2017-08-18 16:38 ` Eduardo Habkost
2017-08-18 16:53 ` Paolo Bonzini
2017-08-21 2:22 ` Lan Tianyu
2017-10-26 12:19 ` Eduardo Habkost
2017-10-26 14:27 ` Michael S. Tsirkin
2017-10-27 1:30 ` Lan Tianyu
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=34042934-782b-6bcc-b9b2-de7a1816cfb7@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=tianyu.lan@intel.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).