public inbox for linux-kernel@vger.kernel.org
 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 2/3] kvm: don't register wildcard MMIO EVENTFD on two buses
Date: Mon, 24 Aug 2015 11:29:29 +0800	[thread overview]
Message-ID: <55DA8F99.106@redhat.com> (raw)
In-Reply-To: <20150821112946.64ae6f7b.cornelia.huck@de.ibm.com>



On 08/21/2015 05:29 PM, Cornelia Huck wrote:
> On Fri, 21 Aug 2015 16:03:52 +0800
> Jason Wang <jasowang@redhat.com> wrote:
>
>
>> diff --git a/virt/kvm/eventfd.c b/virt/kvm/eventfd.c
>> index 9ff4193..834a409 100644
>> --- a/virt/kvm/eventfd.c
>> +++ b/virt/kvm/eventfd.c
>> @@ -838,11 +838,6 @@ kvm_assign_ioeventfd(struct kvm *kvm, struct kvm_ioeventfd *args)
>>  
>>  	kvm_iodevice_init(&p->dev, &ioeventfd_ops);
>>  
>> -	ret = kvm_io_bus_register_dev(kvm, bus_idx, p->addr, p->length,
>> -				      &p->dev);
>> -	if (ret < 0)
>> -		goto unlock_fail;
>> -
>>  	/* When length is ignored, MMIO is also put on a separate bus, for
>>  	 * faster lookups.
> You probably want to change this comment as well?

Yes.

>
>>  	 */
>> @@ -850,9 +845,15 @@ kvm_assign_ioeventfd(struct kvm *kvm, struct kvm_ioeventfd *args)
> Unfortunately snipped by diff, but the check here is on !len && !PIO,
> which only does the desired thing as VIRTIO_CCW always uses len == 8.
> Should the check be for !len && MMIO instead?

I think the answer depends on whether len == 0 is valid for ccw. If not
we can fail the assign earlier. Since even without this patch, if
userspace tries to register a dev with len equals to zero, it will also
be registered to KVM_FAST_MMIO_BUS. If yes, we need check as you
suggested here.

>
>>  		ret = kvm_io_bus_register_dev(kvm, KVM_FAST_MMIO_BUS,
>>  					      p->addr, 0, &p->dev);
>>  		if (ret < 0)
>> -			goto register_fail;
>> +			goto unlock_fail;
>> +	} else {
>> +		ret = kvm_io_bus_register_dev(kvm, bus_idx, p->addr, p->length,
>> +					      &p->dev);
>> +		if (ret < 0)
>> +			goto unlock_fail;
>>  	}
> Hm... maybe the following would be more obvious:
>
> my_bus = (p->length == 0) && (bus_idx == KVM_MMIO_BUS) ? KVM_FAST_MMIO_BUS : bus_idx;
> ret = kvm_io_bus_register_dev(kvm, my_bus, p->addr, p->length, &pdev->dev); 
>
>>  
>> +
>>  	kvm->buses[bus_idx]->ioeventfd_count++;
>>  	list_add_tail(&p->list, &kvm->ioeventfds);
> (...)
>
>> @@ -900,10 +899,11 @@ kvm_deassign_ioeventfd(struct kvm *kvm, struct kvm_ioeventfd *args)
>>  		if (!p->wildcard && p->datamatch != args->datamatch)
>>  			continue;
>>  
>> -		kvm_io_bus_unregister_dev(kvm, bus_idx, &p->dev);
>>  		if (!p->length) {
>>  			kvm_io_bus_unregister_dev(kvm, KVM_FAST_MMIO_BUS,
>>  						  &p->dev);
>> +		} else {
>> +			kvm_io_bus_unregister_dev(kvm, bus_idx, &p->dev);
>>  		}
> Similar comments here... do you want to check for bus_idx ==
> KVM_MMIO_BUS as well?

Good catch. I think keep the original code as is will be also ok to
solve this. (with changing the bus_idx to KVM_FAST_MMIO_BUS during
registering if it was an wildcard mmio).

>
>>  		kvm->buses[bus_idx]->ioeventfd_count--;
>>  		ioeventfd_release(p);


  reply	other threads:[~2015-08-24  3:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21  8:03 [PATCH 1/3] kvm: use kmalloc() instead of kzalloc() during iodev register/unregister Jason Wang
2015-08-21  8:03 ` [PATCH 2/3] kvm: don't register wildcard MMIO EVENTFD on two buses Jason Wang
2015-08-21  9:29   ` Cornelia Huck
2015-08-24  3:29     ` Jason Wang [this message]
2015-08-24 14:05       ` Cornelia Huck
2015-08-25  3:04         ` Jason Wang
2015-08-25  7:36           ` Jason Wang
2015-08-21  8:03 ` [PATCH 3/3] kvm: add tracepoint for fast mmio 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=55DA8F99.106@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