xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Matt Wilson <msw@linux.com>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [RFC PATCH 1/5] Support for running secondary emulators
Date: Mon, 3 Mar 2014 14:41:19 -0800	[thread overview]
Message-ID: <20140303224117.GA6867@u109add4315675089e695.ant.amazon.com> (raw)
In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD02612E0@AMSPEX01CL01.citrite.net>

On Mon, Mar 03, 2014 at 01:34:41PM +0000, Paul Durrant wrote:
> > -----Original Message-----
> > From: Matt Wilson [mailto:mswilson@gmail.com] On Behalf Of Matt Wilson
> > Sent: 01 March 2014 22:25
> > To: Paul Durrant
> > Cc: xen-devel@lists.xen.org
> > Subject: Re: [Xen-devel] [RFC PATCH 1/5] Support for running secondary
> > emulators
> > 
> > On Thu, Jan 30, 2014 at 02:19:45PM +0000, Paul Durrant wrote:
> > > This patch series adds the ioreq server interface which I mentioned in
> > > my talk at the Xen developer summit in Edinburgh at the end of last year.
> > > The code is based on work originally done by Julien Grall but has been
> > > re-written to allow existing versions of QEMU to work unmodified.
> > >
> > [...]
> > 
> > Hi Paul,
> > 
> > I'm coming back to play with this after a few weeks and I'm having
> > trouble getting things going. It seems that I'm crashing early when
> > hvmloader is programming the PCI-ISA bridge link routes.

[...]

> > Any quick ideas before I go instrumenting things?
> > 
> 
> 
> Matt,
> 
> I've re-worked the patches a bit and am about to submit them non-RFC
> this time. I had a look at the shared page setup given what you saw
> and I can't find a memset anywhere to init the shared ioreq state so
> I suspect your problem is just uninitialized mem (and I guess I may
> not have seen it as I usually only run up a couple of VMs before I
> need to do a host reboot so I'm probably getting freshly scrubbed
> pages every time). So, I'll stick a memset in my new patch and
> hopefully you can give the new code a spin once I've posted it.

I'm not sure... I tossed a scrub_one_page(page); in hvm_set_ioreq_page()
but that didn't seem to help.

I'll give your next series a spin when you post them (or push to your
git repository).

--msw

  reply	other threads:[~2014-03-03 22:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 14:19 [RFC PATCH 1/5] Support for running secondary emulators Paul Durrant
2014-01-30 14:19 ` [RFC PATCH 1/5] ioreq-server: centralize access to ioreq structures Paul Durrant
2014-01-30 14:32   ` Andrew Cooper
2014-01-30 14:35     ` Paul Durrant
2014-02-07  4:53   ` Matt Wilson
2014-02-07  9:24     ` Paul Durrant
2014-01-30 14:19 ` [RFC PATCH 2/5] ioreq-server: create basic ioreq server abstraction Paul Durrant
2014-01-30 15:03   ` Andrew Cooper
2014-01-30 15:17     ` Paul Durrant
2014-01-30 14:19 ` [RFC PATCH 3/5] ioreq-server: on-demand creation of ioreq server Paul Durrant
2014-01-30 15:21   ` Andrew Cooper
2014-01-30 15:32     ` Paul Durrant
2014-01-30 14:19 ` [RFC PATCH 4/5] ioreq-server: add support for multiple servers Paul Durrant
2014-01-30 15:46   ` Andrew Cooper
2014-01-30 15:56     ` Paul Durrant
2014-01-30 14:19 ` [RFC PATCH 5/5] ioreq-server: bring the PCI hotplug controller implementation into Xen Paul Durrant
2014-01-30 15:55   ` Andrew Cooper
2014-01-30 16:06     ` Paul Durrant
2014-01-30 16:38       ` Jan Beulich
2014-01-30 16:42         ` Paul Durrant
2014-01-30 14:23 ` [RFC PATCH 1/5] Support for running secondary emulators Paul Durrant
2014-03-01 22:24 ` Matt Wilson
2014-03-03 13:34   ` Paul Durrant
2014-03-03 22:41     ` Matt Wilson [this message]
2014-03-04 10:11       ` Paul Durrant

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=20140303224117.GA6867@u109add4315675089e695.ant.amazon.com \
    --to=msw@linux.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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).