All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: xen-devel@lists.xen.org, ross.philipson@citrix.com,
	stefano.stabellini@eu.citrix.com
Subject: Re: [QEMU-traditional] ACPI AML code races with QEMU updating the vCPU count when hotplugging more than ~14 VCPUs.
Date: Fri, 10 May 2013 11:01:44 -0400	[thread overview]
Message-ID: <20130510150144.GM19520@phenom.dumpdata.com> (raw)
In-Reply-To: <20130509235047.659a5867@thinkpad>

> > Then if the other events are triggered we can just check the
> > gpe_state.cpus_state against what XenBus thinks and if they
> > are the same just return without doing the qemu_irq_pulse.
> > 
> > Thoughts?
> Could you check if switching from level to edge handling in AML helps?
> http://git.qemu.org/?p=seabios.git;a=commit;h=9c6635bd48d39a1d17d0a73df6e577ef6bd0037c

Sadly did not help. I am thinking just to try out the outline of
the code I wrote and see how it works. 

BTW, this is with the traditional Xen QEMU. I couldn't get the SeaBIOS
QEMU to work with this and I think that is b/c the XenStore monitoring
of the CPUs availability is just not there.

Ah, it might be via the QMP layer thingy. I should look in that.

> 
> 
> -- 
> Regards,
>   Igor
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
> 

  reply	other threads:[~2013-05-10 15:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-09 20:47 [QEMU-traditional] ACPI AML code races with QEMU updating the vCPU count when hotplugging more than ~14 VCPUs Konrad Rzeszutek Wilk
2013-05-09 21:50 ` Igor Mammedov
2013-05-10 15:01   ` Konrad Rzeszutek Wilk [this message]
2013-05-10 13:55 ` upstream QEMU and cpu hotplug Was: " Stefano Stabellini
2013-05-10 17:23   ` 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=20130510150144.GM19520@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=imammedo@redhat.com \
    --cc=ross.philipson@citrix.com \
    --cc=stefano.stabellini@eu.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 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.