From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: xen dependant on pcpu 0 ?
Date: Tue, 12 Oct 2010 18:13:02 +0100 [thread overview]
Message-ID: <1286903582.5663.167.camel@localhost.localdomain> (raw)
In-Reply-To: <20101012164433.GB21567@dumpdata.com>
On Tue, 2010-10-12 at 17:44 +0100, Konrad Rzeszutek Wilk wrote:
> On Tue, Oct 12, 2010 at 06:28:13PM +0200, Sander Eikelenboom wrote:
> > Hi Keir,
> >
> > Does xen and/or the xen console depend on physical cpu 0 ?
>
> Usually the console for Dom0, and I think all other domains go
> through CPU0. Let me CC Ian here, who has been mucking in this
> area and found some bugs (and produced fixes).
>
> Ian, that bug you found with not clearing the eventchannel - that
> wouldn't have an impact here, right?
I don't think so. That issue was related to evtchn delivery which is to
VCPUs not PCPUs. I don't think it was specific to VCPU0 either -- it
just happened that the particular evtchn was generally tied to VCPU0 by
default.
I don't think the problem would happen for PIRQs anyway since the
->startup method for that IRQ chip includes an explicit rebind of the
evtchn to a VCPU, it's only dynirqs which have the issue.
Ian.
next prev parent reply other threads:[~2010-10-12 17:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 16:28 xen dependant on pcpu 0 ? Sander Eikelenboom
2010-10-12 16:44 ` Konrad Rzeszutek Wilk
2010-10-12 17:13 ` Ian Campbell [this message]
2010-10-12 18:50 ` Sander Eikelenboom
2010-10-12 19:37 ` Sander Eikelenboom
2010-10-13 13:36 ` Sander Eikelenboom
2010-10-13 14:26 ` Sander Eikelenboom
2010-10-13 14:41 ` Jan Beulich
[not found] ` <31342487.20101013170345@eikelenboom.it>
[not found] ` <4CB5EBC3020000780001CEC6@vpn.id2.novell.com>
2010-10-13 15:41 ` Sander Eikelenboom
2010-10-13 16:08 ` Jan Beulich
2010-10-13 14:26 ` Jan Beulich
2010-10-13 15:00 ` Jiang, Yunhong
2010-10-13 15:31 ` 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=1286903582.5663.167.camel@localhost.localdomain \
--to=ian.campbell@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux@eikelenboom.it \
--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.