xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>,
	Anthony PERARD <anthony.perard@citrix.com>
Cc: Xen Devel <xen-devel@lists.xen.org>, Keir Fraser <keir@xen.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH V3] xen: Fix BUFIOREQ evtchn init for a stubdom.
Date: Mon, 02 Jul 2012 20:37:51 +0100	[thread overview]
Message-ID: <CC17B71F.37610%keir.xen@gmail.com> (raw)
In-Reply-To: <4FF1E1F1020000780008D29B@nat28.tlf.novell.com>

On 02/07/2012 17:01, "Jan Beulich" <JBeulich@suse.com> wrote:

>>>> On 02.07.12 at 17:58, "Jan Beulich" <JBeulich@suse.com> wrote:
>>> @@ -3775,19 +3790,16 @@ long do_hvm_op(unsigned long op,
>>> XEN_GUEST_HANDLE(void) arg)
>>>                  rc = 0;
>>>                  domain_pause(d); /* safe to change per-vcpu xen_port */
>>>                  iorp = &d->arch.hvm_domain.ioreq;
>>> +                if (d->vcpu[0])
>>> +                    hvm_replace_event_channel(d->vcpu[0], a.value,
>>> +              
>>> (int*)&d->vcpu[0]->domain->arch.hvm_domain.params[HVM_PARAM_BUFIOREQ_EVTCHN]
>>> );
>> 
>> Did I overlook this in v2? You clearly need to handle the error
>> case here (it is being handled, albeit - but that's not your patch's
>> fault - only in a rudimentary way, inside the loop).
> 
> Probably it'll be easiest if I - or Keir if he's faster - add this while
> committing, to save you from posting another version.

I'm travelling so please just go ahead, Jan.

 K.

> Jan
> 

  reply	other threads:[~2012-07-02 19:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-02 15:41 [PATCH V3] xen: Fix BUFIOREQ evtchn init for a stubdom Anthony PERARD
2012-07-02 15:58 ` Jan Beulich
2012-07-02 16:01   ` Jan Beulich
2012-07-02 19:37     ` Keir Fraser [this message]
2012-07-02 16:05   ` Anthony PERARD

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=CC17B71F.37610%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=anthony.perard@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=keir@xen.org \
    --cc=stefano.stabellini@eu.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).