public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: Clarify KVM_ASSIGN_PCI_DEVICE documentation
Date: Thu, 2 Jun 2011 23:04:14 -0300	[thread overview]
Message-ID: <20110603020414.GB7272@amt.cnet> (raw)
In-Reply-To: <4DE79B29.6030609@web.de>

On Thu, Jun 02, 2011 at 04:16:09PM +0200, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> Neither host_irq nor the guest_msi struct are used anymore today.
> Tag the former, drop the latter to avoid confusion.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>  Documentation/virtual/kvm/api.txt |    7 +------
>  1 files changed, 1 insertions(+), 6 deletions(-)
> 
> diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt
> index 2bd06b0..7adc1ac 100644
> --- a/Documentation/virtual/kvm/api.txt
> +++ b/Documentation/virtual/kvm/api.txt
> @@ -1143,15 +1143,10 @@ Assigns an IRQ to a passed-through device.
>  
>  struct kvm_assigned_irq {
>  	__u32 assigned_dev_id;
> -	__u32 host_irq;
> +	__u32 host_irq;		/* ignored (legacy field) */
>  	__u32 guest_irq;
>  	__u32 flags;
>  	union {
> -		struct {
> -			__u32 addr_lo;
> -			__u32 addr_hi;
> -			__u32 data;
> -		} guest_msi;
>  		__u32 reserved[12];
>  	};
>  };

Please update the kernel headers accordingly.


  reply	other threads:[~2011-06-03  2:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 14:16 [PATCH] KVM: Clarify KVM_ASSIGN_PCI_DEVICE documentation Jan Kiszka
2011-06-03  2:04 ` Marcelo Tosatti [this message]
2011-06-03  6:51   ` [PATCH v2] " Jan Kiszka
2011-06-06  8:42     ` Avi Kivity
2011-06-06 19:57       ` Jan Kiszka
2011-06-09  8:13         ` Avi Kivity

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=20110603020414.GB7272@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.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