All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: c/s 20384
Date: Mon, 02 Nov 2009 13:08:36 -0800	[thread overview]
Message-ID: <4AEF4A54.2030806@goop.org> (raw)
In-Reply-To: <4AEEA3BB020000780001D146@vpn.id2.novell.com>

On 11/02/09 00:17, Jan Beulich wrote:
> Keir,
>
> I'm having the impression that this c/s unintentionally modifies behavior in
> certain ways:
>
> - map_vcpu_info() no longer sets evtchn_upcall_mask for a newly mapped
> info struct
> - VCPUOP_initialise no longer fails when a vCPU didn't have a proper info
> struct installed
> - the changes to xen/common/event_channel.c make it so that
> dummy_vcpu_info can be written to, and hence subsequently initialized
> vcpu_info structs would have unpredictable initial state
>   

What's the real changeset id you're referring to?  The small-integer
numbers are only locally valid (and globally by coincidence), and 20384
here doesn't seem at all relevant to your points.

I you're referring to f74f0c1ae8ab, which is  21773 in my tree...

    J

  parent reply	other threads:[~2009-11-02 21:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02  8:17 c/s 20384 Jan Beulich
2009-11-02  9:40 ` Keir Fraser
2009-11-02 21:08 ` Jeremy Fitzhardinge [this message]
2009-11-02 21:39   ` Keir Fraser
2009-11-03 10:09   ` Jan Beulich
2009-11-03 19:06     ` Jeremy Fitzhardinge

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=4AEF4A54.2030806@goop.org \
    --to=jeremy@goop.org \
    --cc=JBeulich@novell.com \
    --cc=keir.fraser@eu.citrix.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.