From: Paul Larson <pl@us.ibm.com>
To: xen-devel@lists.xensource.com
Subject: Re: APIC handling on x86-64
Date: Tue, 21 Mar 2006 09:26:37 -0600 [thread overview]
Message-ID: <200603210926.39623.pl@us.ibm.com> (raw)
In-Reply-To: <832dd3dbe08a5d13cbdda6a855307af9@cl.cam.ac.uk>
[-- Attachment #1.1: Type: text/plain, Size: 881 bytes --]
On Tuesday 21 March 2006 08:34, Keir Fraser wrote:
> Testing is the scary thing for me. I have no access to Summit or ES7000
> boxes, and I don't know what external testing is being done on those
> systems and on what schedule. For all I know, bugs could be introduced
> and not fixed for an arbitrary time. If I know there is testing
> infrastructure I would like to move closer to x86/64's genapic code
> (which uses generic mechanisms to determine what APIC mode to use) and
> keep the minimal amount possible of default/bigsmp/summit/es7000
> specific subarchitecture code. Still, some incremental progress on that
> path is definitely achievable.
We have not seen this issue on our 2-node 460 or any of our other summit
boxes. However we do have a couple of summit boxes we could use for testing
if you have some code to throw at us.
Thanks,
Paul Larson
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-03-21 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 14:23 APIC handling on x86-64 Jan Beulich
2006-03-21 14:34 ` Keir Fraser
2006-03-21 15:26 ` Paul Larson [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-21 15:30 Puthiyaparambil, Aravindh
2006-03-21 15:38 ` Keir Fraser
2006-03-21 14:47 Jan Beulich
2006-03-20 13:53 Jan Beulich
2006-03-20 16:00 ` Keir Fraser
2006-03-20 16:21 ` Keir Fraser
2006-03-19 19:15 Jan Beulich
2006-03-19 23:45 ` Keir Fraser
2006-03-17 16:49 Jan Beulich
2006-03-17 17:06 ` Keir Fraser
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=200603210926.39623.pl@us.ibm.com \
--to=pl@us.ibm.com \
--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.