All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] xen, apic: Setup our own APIC driver and validator for APIC IDs.
Date: Mon, 02 Mar 2015 12:34:53 -0500	[thread overview]
Message-ID: <54F49F3D.2030201@oracle.com> (raw)
In-Reply-To: <20150302173257.GQ3418@l.oracle.com>

On 03/02/2015 12:32 PM, Konrad Rzeszutek Wilk wrote:
> On Mon, Mar 02, 2015 at 05:25:55PM +0000, David Vrabel wrote:
>
>> I've only given the briefest of smoke-tests.  It would probably be a
>> good idea to queue this branch for some testing early.
> <nods>
>
> I did the 'perf' test which does use the IPI in an PV guest and
> in dom0 and it worked. And naturally bootup on an machine with an unholy
> amount of CPUs (x2APIC) - and also smaller ones.
>
> And then the smoke-test that Boris does as well (on a sister lab setup).
>
> But it would be good to make sure this patch does not blow anything up.

I will queue it for overnight runs once it shows up in the tree.


-boris

  reply	other threads:[~2015-03-02 17:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 21:14 [PATCH] xen,apic: Setup our own APIC driver and validator for APIC IDs Konrad Rzeszutek Wilk
2015-03-02 11:24 ` [Xen-devel] [PATCH] xen, apic: " David Vrabel
2015-03-02 14:22   ` Konrad Rzeszutek Wilk
     [not found]     ` <54F47646.1070707@citrix.com>
2015-03-02 17:06       ` Konrad Rzeszutek Wilk
2015-03-02 17:25         ` David Vrabel
2015-03-02 17:32           ` Konrad Rzeszutek Wilk
2015-03-02 17:34             ` Boris Ostrovsky [this message]
2015-03-02 14:22   ` Konrad Rzeszutek Wilk
2015-03-02 11:24 ` David Vrabel
  -- strict thread matches above, loose matches on Subject: below --
2015-02-27 21:14 Konrad Rzeszutek Wilk

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=54F49F3D.2030201@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.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.