From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Wei Liu <liuw@liuw.name>
Cc: xen-devel@lists.xensource.com,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH 2/2] libxc: enabling emulated MSI injection
Date: Thu, 26 May 2011 08:34:52 -0400 [thread overview]
Message-ID: <20110526123452.GA3386@dumpdata.com> (raw)
In-Reply-To: <BANLkTi=PDEZzOOXsmzYVfuCnNf9uaOt_EQ@mail.gmail.com>
On Thu, May 26, 2011 at 11:09:43AM +0800, Wei Liu wrote:
> commit 67038b5b18096b3bdcda7fe393d1be6a91dc75a6
> Author: Wei Liu <liuw@liuw.name>
> Date: Thu May 26 10:27:41 2011 +0800
>
> libxc: add new operation in HVMOP to deliver emulated MSI.
What is the purpose of this call?
>
> Signed-off-by: Wei Liu <liuw@liuw.name>
>
> diff --git a/tools/libxc/xc_misc.c b/tools/libxc/xc_misc.c
> index b87bbc0..38af397 100644
> --- a/tools/libxc/xc_misc.c
> +++ b/tools/libxc/xc_misc.c
> @@ -417,6 +417,35 @@ int xc_hvm_set_pci_link_route(
> return rc;
> }
>
> +int xc_hvm_inj_msi(
> + xc_interface *xch, domid_t dom, uint64_t addr, uint32_t data)
> +{
> + DECLARE_HYPERCALL;
> + DECLARE_HYPERCALL_BUFFER(struct xen_hvm_inj_msi, arg);
> + int rc;
> +
> + arg = xc_hypercall_buffer_alloc(xch, arg, sizeof(*arg));
> + if ( arg == NULL )
> + {
> + PERROR("Could not allocate memory for xc_hvm_inj_msi hypercall");
> + return -1;
> + }
> +
> + hypercall.op = __HYPERVISOR_hvm_op;
> + hypercall.arg[0] = HVMOP_inj_msi;
> + hypercall.arg[1] = HYPERCALL_BUFFER_AS_ARG(arg);
> +
> + arg->domid = dom;
> + arg->addr = addr;
> + arg->data = data;
Shouldn't those be done before you make the HYPERCALL_BUFFER_AS_ARG
in case they get bounced?
> +
> + rc = do_xen_hypercall(xch, &hypercall);
> +
> + xc_hypercall_buffer_free(xch, arg);
> +
> + return rc;
> +}
> +
> int xc_hvm_track_dirty_vram(
> xc_interface *xch, domid_t dom,
> uint64_t first_pfn, uint64_t nr,
> diff --git a/tools/libxc/xenctrl.h b/tools/libxc/xenctrl.h
> index 9a4355f..2442c84 100644
> --- a/tools/libxc/xenctrl.h
> +++ b/tools/libxc/xenctrl.h
> @@ -1387,6 +1387,8 @@ int xc_hvm_set_isa_irq_level(
> int xc_hvm_set_pci_link_route(
> xc_interface *xch, domid_t dom, uint8_t link, uint8_t isa_irq);
>
> +int xc_hvm_inj_msi(
> + xc_interface *xch, domid_t dom, uint64_t addr, uint32_t data);
>
> /*
> * Track dirty bit changes in the VRAM area
>
> --
> Best regards
> Wei Liu
> Twitter: @iliuw
> Site: http://liuw.name
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-05-26 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 3:09 [PATCH 2/2] libxc: enabling emulated MSI injection Wei Liu
2011-05-26 12:34 ` Konrad Rzeszutek Wilk [this message]
2011-05-26 12:56 ` Wei Liu
2011-05-26 13:05 ` Konrad Rzeszutek Wilk
2011-05-26 12:59 ` 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=20110526123452.GA3386@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=liuw@liuw.name \
--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).