linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: gleb@kernel.org, pbonzini@redhat.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH V2 2/3] kvm: don't register wildcard MMIO EVENTFD on two buses
Date: Tue, 25 Aug 2015 17:06:32 +0800	[thread overview]
Message-ID: <55DC3018.9000807@redhat.com> (raw)
In-Reply-To: <20150825102018.0b32b9bd.cornelia.huck@de.ibm.com>



On 08/25/2015 04:20 PM, Cornelia Huck wrote:
> On Tue, 25 Aug 2015 15:47:14 +0800
> Jason Wang <jasowang@redhat.com> wrote:
>
>> diff --git a/virt/kvm/eventfd.c b/virt/kvm/eventfd.c
>> index 9ff4193..95f2901 100644
>> --- a/virt/kvm/eventfd.c
>> +++ b/virt/kvm/eventfd.c
>> @@ -762,13 +762,15 @@ ioeventfd_check_collision(struct kvm *kvm, struct _ioeventfd *p)
>>  	return false;
>>  }
>>
>> -static enum kvm_bus ioeventfd_bus_from_flags(__u32 flags)
>> +static enum kvm_bus ioeventfd_bus_from_flags(struct kvm_ioeventfd *args)
> ioeventfd_bus_from_args()? But _from_flags() is not wrong either :)
>
>>  {
>> -	if (flags & KVM_IOEVENTFD_FLAG_PIO)
>> +	if (args->flags & KVM_IOEVENTFD_FLAG_PIO)
>>  		return KVM_PIO_BUS;
>> -	if (flags & KVM_IOEVENTFD_FLAG_VIRTIO_CCW_NOTIFY)
>> +	if (args->flags & KVM_IOEVENTFD_FLAG_VIRTIO_CCW_NOTIFY)
>>  		return KVM_VIRTIO_CCW_NOTIFY_BUS;
>> -	return KVM_MMIO_BUS;
>> +	if (args->len)
>> +		return KVM_MMIO_BUS;
>> +	return KVM_FAST_MMIO_BUS;
> Hm...
>
> /* When length is ignored, MMIO is put on a separate bus, for
>  * faster lookups.
>  */
> return args->len ? KVM_MMIO_BUS : KVM_FAST_MMIO_BUS;
>
>>  }
>>
>>  static int
> This version of the patch looks nice and compact. Regardless whether
> you want to follow my (minor) style suggestions, consider this patch
>
> Acked-by: Cornelia Huck <cornelia.huck@de.ibm.com>
>

Thanks for the review. V3 posted :)

  reply	other threads:[~2015-08-25  9:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25  7:47 [PATCH V2 1/3] kvm: use kmalloc() instead of kzalloc() during iodev register/unregister Jason Wang
2015-08-25  7:47 ` [PATCH V2 2/3] kvm: don't register wildcard MMIO EVENTFD on two buses Jason Wang
2015-08-25  8:20   ` Cornelia Huck
2015-08-25  9:06     ` Jason Wang [this message]
2015-08-25 11:33   ` Michael S. Tsirkin
2015-08-26  5:07     ` Jason Wang
2015-08-25  7:47 ` [PATCH V2 3/3] kvm: add tracepoint for fast mmio Jason Wang
2015-08-25 11:34   ` Michael S. Tsirkin
2015-08-26  5:08     ` Jason Wang
2015-08-25 15:29 ` [PATCH V2 1/3] kvm: use kmalloc() instead of kzalloc() during iodev register/unregister Joe Perches
2015-08-26  5:39   ` Jason Wang
2015-08-26  5:45     ` Joe Perches
2015-08-26  5:48       ` Jason Wang

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=55DC3018.9000807@redhat.com \
    --to=jasowang@redhat.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=gleb@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=pbonzini@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 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).