From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH v2] KVM: Clarify KVM_ASSIGN_PCI_DEVICE documentation
Date: Mon, 06 Jun 2011 11:42:28 +0300 [thread overview]
Message-ID: <4DEC92F4.4010305@redhat.com> (raw)
In-Reply-To: <4DE88459.3010205@web.de>
On 06/03/2011 09:51 AM, 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.
>
> diff --git a/include/linux/kvm.h b/include/linux/kvm.h
> index 55ef181..9c9ca7c 100644
> --- a/include/linux/kvm.h
> +++ b/include/linux/kvm.h
> @@ -773,20 +773,14 @@ struct kvm_assigned_pci_dev {
>
> 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];
> };
> };
>
> -
> struct kvm_assigned_msix_nr {
> __u32 assigned_dev_id;
> __u16 entry_nr;
Can we just drop a definition like this? When did we last use this?
(in fact I can't find when we *ever* used this)
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-06-06 8:42 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
2011-06-03 6:51 ` [PATCH v2] " Jan Kiszka
2011-06-06 8:42 ` Avi Kivity [this message]
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=4DEC92F4.4010305@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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.