xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Stefano Stabellini <stefano.stabellini@citrix.com>,
	Xen Devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 0/4] CPU hotplug port from qemu-traditionnal to qemu-xen for 4.3.
Date: Mon, 3 Jun 2013 12:12:52 +0100	[thread overview]
Message-ID: <51AC7A34.3010102@citrix.com> (raw)
In-Reply-To: <1370248908.404.11.camel@zakaz.uk.xensource.com>

On 03/06/13 09:41, Ian Campbell wrote:
>> > BUG: There is an issue with SeaBIOS (used with qemu-xen). At SMP
>> > initialisation, SeaBIOS will count the number of CPU running, and the number is
>> > always equal to maxvcpu when SeaBIOS expect less. This happen when we have
>> > something like:
>> > vcpus = 2
>> > maxvcpus = 8
>> > in the VM config file. Linux is fine with this and will use only $vcpus.  So
>> > the probleme is: an infinit loop in SeaBIOS.
> I'm a bit confused -- if SeaBIOS has an infinite loop how do you even
> get to know Linux is OK?
> 
> Do you have a fix for SeaBIOS, I don't see it in this series.

The thing is, I don't know how to fix this bug.  This is why there is no
patch.

The probleme is this loop:
> u8 cmos_smp_count = inb_cmos(CMOS_BIOS_SMP_COUNT);
> while (cmos_smp_count + 1 != readl(&CountCPUs))
>   ;

where CountCPUs is incremented by each CPU by a small piece of code and
cmos_smp_count is equal to 1, which is the number of expected vcpus-1.
CountCPUs always go up to maxvcpus under Xen.

I could simply replace the '!=' by a '>' but it feel like a workaround...

-- 
Anthony PERARD

  reply	other threads:[~2013-06-03 11:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-31 16:33 [PATCH 0/4] CPU hotplug port from qemu-traditionnal to qemu-xen for 4.3 Anthony PERARD
2013-05-31 16:33 ` [PATCH 1/4] HVM vcpu add/remove: qemu logic for vcpu add/revmoe Anthony PERARD
2013-05-31 21:19   ` Konrad Rzeszutek Wilk
2013-06-03 10:23   ` Stefano Stabellini
2013-05-31 16:33 ` [PATCH 2/4] Fix vcpu hotplug bug: get correct vcpu_avail bitmap Anthony PERARD
2013-05-31 16:33 ` [PATCH 3/4] Update vcpu hotplug logic Anthony PERARD
2013-05-31 21:16   ` Konrad Rzeszutek Wilk
2013-05-31 16:33 ` [PATCH 4/4] Implement 'xm vcpu-set' command for HVM guest Anthony PERARD
2013-05-31 21:14   ` Konrad Rzeszutek Wilk
2013-06-03  8:40   ` Ian Campbell
2013-06-03 10:24   ` Stefano Stabellini
2013-05-31 16:39 ` [PATCH] libxl: Use -vcpu_avail with qemu-xen Anthony PERARD
2013-06-03  8:37   ` Ian Campbell
2013-06-03 10:10     ` Stefano Stabellini
2013-06-03 13:49     ` Anthony PERARD
2013-05-31 17:20 ` [PATCH 0/4] CPU hotplug port from qemu-traditionnal to qemu-xen for 4.3 Anthony PERARD
2013-06-03  8:37   ` Ian Campbell
     [not found] ` <51A8DA91.1080601@citrix.com>
2013-05-31 21:16   ` Konrad Rzeszutek Wilk
2013-06-03  8:41 ` Ian Campbell
2013-06-03 11:12   ` Anthony PERARD [this message]
2013-06-03 10:13 ` Stefano Stabellini

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=51AC7A34.3010102@citrix.com \
    --to=anthony.perard@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=xen-devel@lists.xen.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).