From: Avi Kivity <avi@redhat.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 1/3] KVM: Ioctls for init MSI-X entry
Date: Wed, 18 Feb 2009 10:32:04 +0000 [thread overview]
Message-ID: <499BE3A4.3010402@redhat.com> (raw)
In-Reply-To: <1234950262-4142-2-git-send-email-sheng@linux.intel.com>
Sheng Yang wrote:
> Introduce KVM_SET_MSIX_NR and KVM_SET_MSIX_ENTRY two ioctls.
>
> This two ioctls are used by userspace to specific guest device MSI-X entry
> number and correlate MSI-X entry with GSI during the initialization stage.
>
> MSI-X should be well initialzed before enabling.
>
> Don't support change MSI-X entry number for now.
>
>
Sorry, this has been reviewed quite a bit but I found a few issues:
> diff --git a/include/linux/kvm.h b/include/linux/kvm.h
> index 2163b3d..a2dfbe0 100644
> --- a/include/linux/kvm.h
> +++ b/include/linux/kvm.h
> @@ -475,6 +475,8 @@ struct kvm_irq_routing {
> #define KVM_ASSIGN_IRQ _IOR(KVMIO, 0x70, \
> struct kvm_assigned_irq)
> #define KVM_REINJECT_CONTROL _IO(KVMIO, 0x71)
> +#define KVM_SET_MSIX_NR _IOR(KVMIO, 0x72, struct kvm_assigned_msix_nr)
> +#define KVM_SET_MSIX_ENTRY _IOR(KVMIO, 0x73, struct kvm_assigned_msix_entry)
>
KVM_SET_ASSIGNED_... so it's associated with device assignment, not generic.
Should be _IOW, not _IOR. Looks like KVM_ASSIGN_IRQ is broken...
>
> +static int kvm_vm_ioctl_set_msix_nr(struct kvm *kvm,
> + struct kvm_assigned_msix_nr *entry_nr)
> +{
> + int r = 0;
> + struct kvm_assigned_dev_kernel *adev;
> +
> + mutex_lock(&kvm->lock);
> +
> + adev = kvm_find_assigned_dev(&kvm->arch.assigned_dev_head,
> + entry_nr->assigned_dev_id);
> + if (!adev) {
> + r = -EINVAL;
> + goto msix_nr_out;
> + }
> +
> + if (adev->entries_nr == 0) {
> + adev->entries_nr = entry_nr->entry_nr;
> + if (adev->entries_nr == 0 ||
> + adev->entries_nr >= KVM_MAX_MSIX_PER_DEV)
> + goto msix_nr_out;
>
r == 0 here, needs a meaningful error number.
> +
> + adev->host_msix_entries = kzalloc(sizeof(struct msix_entry) *
> + entry_nr->entry_nr,
> + GFP_KERNEL);
> + if (!adev->host_msix_entries) {
> + printk(KERN_ERR "no memory for host msix entries!\n");
> + r = -ENOMEM;
>
Drop the printk, -ENOMEM is enough.
> + goto msix_nr_out;
> + }
> + adev->guest_msix_entries = kzalloc(sizeof(struct msix_entry) *
> + entry_nr->entry_nr,
> + GFP_KERNEL);
> + if (!adev->guest_msix_entries) {
> + printk(KERN_ERR "no memory for host msix entries!\n");
>
Ditto.
> + kfree(adev->host_msix_entries);
> + r = -ENOMEM;
> + goto msix_nr_out;
> + }
> + } else
> + printk(KERN_WARNING "kvm: not allow recall set msix nr!\n");
>
Drop printk, add error.
> +msix_nr_out:
> + mutex_unlock(&kvm->lock);
> + return r;
> +}
> +
> +static int kvm_vm_ioctl_set_msix_entry(struct kvm *kvm,
> + struct kvm_assigned_msix_entry *entry)
> +{
> + int r = 0, i;
> + struct kvm_assigned_dev_kernel *adev;
> +
> + mutex_lock(&kvm->lock);
> +
> + adev = kvm_find_assigned_dev(&kvm->arch.assigned_dev_head,
> + entry->assigned_dev_id);
> +
> + if (!adev) {
> + r = -EINVAL;
> + goto msix_entry_out;
> + }
> +
> + for (i = 0; i < adev->entries_nr; i++)
> + if (adev->guest_msix_entries[i].vector == 0 ||
> + adev->guest_msix_entries[i].entry == entry->entry) {
> + adev->guest_msix_entries[i].entry = entry->entry;
> + adev->guest_msix_entries[i].vector = entry->gsi;
> + adev->host_msix_entries[i].entry = entry->entry;
> + break;
> + }
> + if (i == adev->entries_nr) {
> + printk(KERN_ERR "kvm: Too much entries for MSI-X!\n");
>
Drop.
> + r = -ENOSPC;
> + goto msix_entry_out;
> + }
> +
> +msix_entry_out:
> + mutex_unlock(&kvm->lock);
> +
> + return r;
> +}
> +
> static long kvm_vcpu_ioctl(struct file *filp,
> unsigned int ioctl, unsigned long arg)
> {
> @@ -1917,7 +1998,29 @@ static long kvm_vm_ioctl(struct file *filp,
> vfree(entries);
> break;
> }
> +#ifdef KVM_CAP_DEVICE_MSIX
> + case KVM_SET_MSIX_NR: {
> + struct kvm_assigned_msix_nr entry_nr;
> + r = -EFAULT;
> + if (copy_from_user(&entry_nr, argp, sizeof entry_nr))
> + goto out;
> + r = kvm_vm_ioctl_set_msix_nr(kvm, &entry_nr);
> + if (r)
> + goto out;
> + break;
> + }
> + case KVM_SET_MSIX_ENTRY: {
> + struct kvm_assigned_msix_entry entry;
> + r = -EFAULT;
> + if (copy_from_user(&entry, argp, sizeof entry))
> + goto out;
> + r = kvm_vm_ioctl_set_msix_entry(kvm, &entry);
> + if (r)
> + goto out;
> + break;
> + }
> #endif
> +#endif /* KVM_CAP_IRQ_ROUTING */
> default:
> r = kvm_arch_vm_ioctl(filp, ioctl, arg);
> }
>
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-02-18 10:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 9:44 [PATCH 0/3 v3] MSI-X enabling Sheng Yang
2009-02-18 9:44 ` [PATCH 1/3] KVM: Ioctls for init MSI-X entry Sheng Yang
2009-02-18 10:32 ` Avi Kivity [this message]
2009-02-18 9:44 ` [PATCH 2/3] KVM: Add gsi_msg_pending_bitmap for MSI-X Sheng Yang
2009-02-18 11:00 ` Avi Kivity
2009-02-18 11:13 ` Sheng Yang
2009-02-18 11:29 ` Avi Kivity
2009-02-18 11:38 ` Sheng Yang
2009-02-18 9:44 ` [PATCH 3/3] KVM: Enable MSI-X for KVM assigned device Sheng Yang
2009-02-18 10:45 ` Avi Kivity
2009-02-18 12:24 ` Sheng Yang
2009-02-18 12:36 ` Avi Kivity
2009-02-18 12:52 ` Sheng Yang
-- strict thread matches above, loose matches on Subject: below --
2009-02-25 9:22 [PATCH 0/3 v4][Resend] MSI-X enabling Sheng Yang
2009-02-25 9:22 ` [PATCH 1/3] KVM: Ioctls for init MSI-X entry Sheng Yang
2009-02-11 8:08 [PATCH 0/3 v2] MSI-X enabling Sheng Yang
2009-02-11 8:08 ` [PATCH 1/3] KVM: Ioctls for init MSI-X entry Sheng Yang
2009-02-11 12:44 ` Avi Kivity
2009-02-12 6:28 ` Sheng Yang
2009-02-12 10:07 ` Sheng Yang
2009-02-12 18:46 ` Marcelo Tosatti
2009-02-16 3:18 ` Sheng Yang
2009-02-16 5:49 ` Sheng Yang
2009-02-16 23:23 ` Marcelo Tosatti
2009-02-17 1:35 ` Sheng Yang
2009-02-17 1:36 ` Sheng Yang
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=499BE3A4.3010402@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=sheng@linux.intel.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.