From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 3 of 6] evtchn delivery on HVM
Date: Fri, 23 Apr 2010 11:33:48 -0400 [thread overview]
Message-ID: <20100423153348.GA16823@phenom.dumpdata.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1004231135510.11380@kaball-desktop>
> > * How should CPU0 event-channel notifications be delivered?
> > + * val[63:56] == 0: val[55:0] is a delivery GSI (Global System
> > Interrupt).
> > + * val[63:56] == 1: val[55:0] is a delivery PCI INTx line, as follows:
> > + * Domain = val[47:32], Bus = val[31:16],
> > + * DevFn = val[15: 8], IntX = val[ 1: 0]
> > + * If val == 0 then CPU0 event-channel notifications are not delivered.
> >
> > I don't see val[63:56] == 2 ?
> >
>
> the comment on the other patch needs to be update as well
Yup, and it looks that this also needs a patch to xen-unstable.hg as that
header file is missing this data too.
prev parent reply other threads:[~2010-04-23 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 15:16 [PATCH 3 of 6] evtchn delivery on HVM Stefano Stabellini
2010-04-22 20:58 ` Konrad Rzeszutek Wilk
2010-04-23 15:30 ` Stefano Stabellini
2010-04-23 15:33 ` Konrad Rzeszutek Wilk [this message]
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=20100423153348.GA16823@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=stefano.stabellini@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.