From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Dr. David Alan Gilbert" <linux@treblig.org>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>,
Grant McWilliams <grantmasterflash@gmail.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
Xen-devel <xen-devel@lists.xensource.com>,
xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: State of Xen in upstream Linux
Date: Thu, 31 Jul 2008 11:45:37 -0700 [thread overview]
Message-ID: <48920851.3080401@goop.org> (raw)
In-Reply-To: <20080731183634.GA27147@gallifrey>
Dr. David Alan Gilbert wrote:
> Does that include things like /proc/cpuinfo? Current Dom0's seem
> to lose some of the physical IDs information from there.
Dom0's vcpus don't necessarily have any fixed relationship to the
underlying physical cpus, so there's no real way they could. Dom0 might
not even have as many vcpus as there are pcpus. So I think that's expected.
J
next prev parent reply other threads:[~2008-07-31 18:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 0:51 State of Xen in upstream Linux Jeremy Fitzhardinge
2008-07-31 9:08 ` [Xen-devel] " Daniel P. Berrange
2008-07-31 17:54 ` Grant McWilliams
2008-07-31 18:08 ` [Xen-users] " Jeremy Fitzhardinge
2008-07-31 18:19 ` [Xen-users] Re: [Xen-devel] " Alexey Eremenko
2008-07-31 18:28 ` [Xen-users] " Jeremy Fitzhardinge
2008-07-31 18:48 ` Re: [Xen-devel] " Grant McWilliams
2008-07-31 18:58 ` [Xen-users] " Jeremy Fitzhardinge
2008-07-31 20:07 ` Re: [Xen-devel] " Grant McWilliams
2008-07-31 20:14 ` [Xen-users] " Jeremy Fitzhardinge
2008-07-31 18:36 ` [Xen-users] Re: [Xen-devel] " Dr. David Alan Gilbert
2008-07-31 18:45 ` Jeremy Fitzhardinge [this message]
2008-08-01 8:34 ` Daniel P. Berrange
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=48920851.3080401@goop.org \
--to=jeremy@goop.org \
--cc=berrange@redhat.com \
--cc=grantmasterflash@gmail.com \
--cc=linux@treblig.org \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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 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).