All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: "Cao, Buddy" <buddy.cao@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: RE: XEN 4.1 pci passthru performance regression?
Date: Wed, 1 Jun 2011 13:44:25 +0100	[thread overview]
Message-ID: <1306932265.775.235.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <1306914938.775.212.camel@zakaz.uk.xensource.com>

On Wed, 2011-06-01 at 08:55 +0100, Ian Campbell wrote:
> On Wed, 2011-06-01 at 02:41 +0100, Cao, Buddy wrote:
> > Thanks Ian for you reply.
> >
> > >Are you referring only to control operation performance or also to
> > >actual guest performance?
> >
> > It does not impact actual guest performance, only make vm start and shutdown slow.
> 
> Oh good!
> 
> > >Do you find that guests without any PCI passthrough have also slowed
> > >down or is the issue purely for guests with a passed-through device?
> >
> > The guests without any PCI passthrough works as well as xen4.0.2.
> 
> Also good.
> 
> > I tired xl, but looks it always returns "libxl....." relevant error,
> > and none of the command can run properly
> 
> Well, we should also try and resolve this -- xl is expected to work in
> 4.1. Did you see: http://wiki.xen.org/xenwiki/MigrationGuideToXen4.1+ ?
> 
> Please tell us the specifics of the xl failure.
> 
> I tried starting a PV guest with a passed through device with both xm
> and xl and there was no obvious delay on startup or shutdown.
> Unfortunately I don't have a test box which can do passthrough to HVM
> guests at the moment (I'll see if I can scare one up). In the meantime
> perhaps you could add some extra logging to xend to see where the time
> is spent and/or report the xl failues as requested above.
> 
> Also, please can you try xen-unstable.hg to see if the problem still
> exists there.

I found a suitable box and tested xen-unstable.hg.

xm does seem to suffer from a delay of some sort on startup, but xl
doesn't seem to.

I'm afraid I don't have time to dig into xend any further myself.

Ian.

  reply	other threads:[~2011-06-01 12:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b9bc7c5f-5617-4273-a293-7e5b98fb61d9@orsmsx602.amr.corp.intel.com>
2011-05-30  9:08 ` XEN 4.1 pci passthru performance regression? Cao, Buddy
2011-05-31 12:14   ` Ian Campbell
2011-06-01  1:41     ` Cao, Buddy
2011-06-01  7:55       ` Ian Campbell
2011-06-01 12:44         ` Ian Campbell [this message]
2011-05-30  9:12 ` Any suggesions for "Gfx passthru" on GTS 450? Cao, Buddy
2011-05-30 15:37   ` Pasi Kärkkäinen

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=1306932265.775.235.camel@zakaz.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=buddy.cao@intel.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.