From: Wei Liu <liuw@liuw.name>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH 1/2] Xen: enabling emulated MSI injection
Date: Thu, 26 May 2011 11:30:14 +0800 [thread overview]
Message-ID: <BANLkTikScPedkGW13w_nc4DEHUk0qtQO5A@mail.gmail.com> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1505C9BFA3DDD@shsmsx502.ccr.corp.intel.com>
On Thu, May 26, 2011 at 11:21 AM, Tian, Kevin <kevin.tian@intel.com> wrote:
>> From: Wei Liu
>> Sent: Thursday, May 26, 2011 11:09 AM
>>
>> commit 176dc2a26b4b9dd0fe30fab3b168722766218245
>> Author: Wei Liu <liuw@liuw.name>
>> Date: Thu May 26 10:23:01 2011 +0800
>>
>> x86: Add a new operation in HVMOP to inject emulated MSI.
>>
>> The original vmsi_deliver is renamed to vmsi_deliver_irq. New
>
> in your patch you mean vmsi_deliver_pirq which is inconsistent.
>
>> vmsi_deliver is dedicated to the actually delivering.
>>
>> Signed-off-by: Wei Liu <liuw@liuw.name>
>>
>> --- a/xen/include/public/hvm/hvm_op.h
>> +++ b/xen/include/public/hvm/hvm_op.h
>> @@ -82,11 +82,24 @@ typedef enum {
>> HVMMEM_mmio_dm, /* Reads and write go to the device
>> model */
>> } hvmmem_type_t;
>>
>> +/* MSI injection for emulated devices */
>> +#define HVMOP_inj_msi 6
>> +struct xen_hvm_inj_msi {
>> + /* Domain to be injected */
>> + domid_t domid;
>> + /* Address (0xfeeXXXXX) */
>> + uint64_t addr;
>> + /* Data -- lower 32 bits */
>> + uint32_t data;
>> +};
>> +typedef struct xen_hvm_inj_msi xen_hvm_inj_msi_t;
>> +DEFINE_XEN_GUEST_HANDLE(xen_hvm_inj_msi_t);
>> +
>> /* Following tools-only interfaces may change in future. */
>> #if defined(__XEN__) || defined(__XEN_TOOLS__)
>>
>> /* Track dirty VRAM. */
>> -#define HVMOP_track_dirty_vram 6
>> +#define HVMOP_track_dirty_vram 7
>> struct xen_hvm_track_dirty_vram {
>> /* Domain to be tracked. */
>> domid_t domid;
>
> This breaks backward API compatibility.
>
> Thanks
> Kevin
>
Stefano suggests this rename.
The only function that invokes vmsi_deliver() is hvm_pci_msi_assert(),
IIRC. That has been taken care of.
--
Best regards
Wei Liu
Twitter: @iliuw
Site: http://liuw.name
next prev parent reply other threads:[~2011-05-26 3:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 3:08 [PATCH 1/2] Xen: enabling emulated MSI injection Wei Liu
2011-05-26 3:21 ` Tian, Kevin
2011-05-26 3:30 ` Wei Liu [this message]
2011-05-26 5:26 ` Tian, Kevin
2011-05-26 5:43 ` Wei Liu
2011-05-26 6:31 ` Wei Liu
2011-05-26 8:43 ` Tim Deegan
2011-05-26 9:10 ` Keir Fraser
2011-05-26 11:25 ` Stefano Stabellini
2011-05-26 11:49 ` Keir Fraser
2011-05-26 12:51 ` Wei Liu
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=BANLkTikScPedkGW13w_nc4DEHUk0qtQO5A@mail.gmail.com \
--to=liuw@liuw.name \
--cc=kevin.tian@intel.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 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).