All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Amos Kong <akong@redhat.com>
Cc: kvm@vger.kernel.org, jasowang@redhat.com, mtosatti@redhat.com,
	alex.williamson@redhat.com, levinsasha928@gmail.com
Subject: Re: [PATCH v4] KVM: Resize kvm_io_range array dynamically
Date: Wed, 07 Mar 2012 12:57:51 +0200	[thread overview]
Message-ID: <4F573F2F.4030103@redhat.com> (raw)
In-Reply-To: <20120301070136.28053.71067.stgit@dhcp-8-167.nay.redhat.com>

On 03/01/2012 09:01 AM, Amos Kong wrote:
> kvm_io_bus devices are used for ioevent, pit, pic, ioapic,
> coalesced_mmio.
>
> Currently Qemu only emulates one PCI bus, it contains 32 slots,
> one slot contains 8 functions, maximum of supported PCI devices:
>  1 * 32 * 8 = 256. One virtio-blk takes one iobus device,
> one virtio-net(vhost=on) takes two iobus devices.
> The maximum of coalesced mmio zone is 100, each zone
> has an iobus devices. So 300 io_bus devices are not enough.
>
> This patch makes the kvm_io_range array can be resized dynamically.
> Set an upper bounds for kvm_io_range to limit userspace.
> 1000 is a very large limit and not bloat the typical user.
>

Please separate the change to 1000 devs to a new patch.

>  
> +#define NR_IOBUS_DEVS 1000
> +
>  struct kvm_io_bus {
>  	int                   dev_count;
> -#define NR_IOBUS_DEVS 300
> -	struct kvm_io_range range[NR_IOBUS_DEVS];
> +	struct kvm_io_range range[];
>  };
>  
>  enum kvm_bus {
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index e4431ad..1baed68 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -2389,9 +2389,6 @@ int kvm_io_bus_sort_cmp(const void *p1, const void *p2)
>  int kvm_io_bus_insert_dev(struct kvm_io_bus *bus, struct kvm_io_device *dev,
>  			  gpa_t addr, int len)
>  {
> -	if (bus->dev_count == NR_IOBUS_DEVS)
> -		return -ENOSPC;
> -
>  	bus->range[bus->dev_count++] = (struct kvm_io_range) {
>  		.addr = addr,
>  		.len = len,
> @@ -2491,10 +2488,14 @@ int kvm_io_bus_register_dev(struct kvm *kvm, enum kvm_bus bus_idx, gpa_t addr,
>  	struct kvm_io_bus *new_bus, *bus;
>  
>  	bus = kvm->buses[bus_idx];
> -	if (bus->dev_count > NR_IOBUS_DEVS-1)
> +	if (bus->dev_count > NR_IOBUS_DEVS - 1)
>  		return -ENOSPC;
>  
> -	new_bus = kmemdup(bus, sizeof(struct kvm_io_bus), GFP_KERNEL);
> +	new_bus = kzalloc(sizeof(*bus) + ((bus->dev_count + 1) *
> +			  sizeof(struct kvm_io_range)), GFP_KERNEL);
> +	if (new_bus)
> +		memcpy(new_bus, bus, sizeof(*bus) + (bus->dev_count *
> +		       sizeof(struct kvm_io_range)));

This will be cleaner if you move the memcmp() after the check just below.

>  	if (!new_bus)
>  		return -ENOMEM;
>  	kvm_io_bus_insert_dev(new_bus, dev, addr, len);
> @@ -2513,26 +2514,28 @@ int kvm_io_bus_unregister_dev(struct kvm *kvm, enum kvm_bus bus_idx,
>  	struct kvm_io_bus *new_bus, *bus;
>  
>  	bus = kvm->buses[bus_idx];
> -
> -	new_bus = kmemdup(bus, sizeof(*bus), GFP_KERNEL);
> -	if (!new_bus)
> -		return -ENOMEM;
> -
>  	r = -ENOENT;
> -	for (i = 0; i < new_bus->dev_count; i++)
> -		if (new_bus->range[i].dev == dev) {
> +	for (i = 0; i < bus->dev_count; i++)
> +		if (bus->range[i].dev == dev) {
>  			r = 0;
> -			new_bus->dev_count--;
> -			new_bus->range[i] = new_bus->range[new_bus->dev_count];
> -			sort(new_bus->range, new_bus->dev_count,
> -			     sizeof(struct kvm_io_range),
> -			     kvm_io_bus_sort_cmp, NULL);
>  			break;
>  		}
>  
> -	if (r) {
> -		kfree(new_bus);
> +	if (r)
>  		return r;
> +
> +	new_bus = kmemdup(bus, sizeof(*bus) + ((bus->dev_count - 1) *
> +			  sizeof(struct kvm_io_range)), GFP_KERNEL);
> +	if (!new_bus)
> +		return -ENOMEM;
> +
> +	new_bus->dev_count--;
> +	/* copy last entry of bus->range to deleted entry spot if
> +	   deleted entry isn't the last entry of bus->range */
> +	if (i != bus->dev_count - 1) {

The check is unneeded - if they compare equal, the copy is a no-op.

> +		new_bus->range[i] = bus->range[bus->dev_count - 1];

> +		sort(new_bus->range, new_bus->dev_count,
> +		     sizeof(struct kvm_io_range), kvm_io_bus_sort_cmp, NULL);
>  	}
>  
>  	rcu_assign_pointer(kvm->buses[bus_idx], new_bus);
>

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2012-03-07 10:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29  5:24 [PATCH] KVM: Resize kvm_io_bus_range array dynamically Amos Kong
2012-02-29  5:50 ` [PATCH v2] KVM: Resize kvm_io_range " Amos Kong
2012-02-29 13:30 ` [PATCH v3] " Amos Kong
2012-02-29 14:19   ` Jan Kiszka
2012-02-29 15:22     ` Amos Kong
2012-02-29 15:29       ` Jan Kiszka
2012-02-29 16:34         ` Amos Kong
2012-03-01  5:19           ` Amos Kong
2012-03-01  7:01 ` [PATCH v4] " Amos Kong
2012-03-01 10:14   ` Sasha Levin
2012-03-01 15:33     ` Alex Williamson
2012-03-07 10:57   ` Avi Kivity [this message]
2012-03-07 12:51     ` Amos Kong
2012-03-07 14:12       ` Avi Kivity
2012-03-07 13:16   ` [PATCH v5 1/2] KVM: resize " Amos Kong
2012-03-07 13:16   ` [PATCH v5 2/2] KVM: set upper bounds for iobus dev to limit userspace Amos Kong
2012-03-07 13:20   ` [RESEND PATCH v5 0/2] fix ENOSPC issue of iobus dev Amos Kong
2012-03-07 13:20     ` [RESEND PATCH v5 1/2] KVM: resize kvm_io_range array dynamically Amos Kong
2012-03-07 13:20     ` [RESEND PATCH v5 2/2] KVM: set upper bounds for iobus dev to limit userspace Amos Kong
2012-03-08  2:03   ` [PATCH v6 0/2] fix ENOSPC issue of iobus dev Amos Kong
2012-03-08  2:03     ` [PATCH v6 1/2] KVM: resize kvm_io_range array dynamically Amos Kong
2012-03-08 23:20       ` Marcelo Tosatti
2012-03-09  4:05         ` Amos Kong
2012-03-08  2:04     ` [PATCH v6 2/2] KVM: set upper bounds for iobus dev to limit userspace Amos Kong
2012-03-09  4:17   ` [PATCH v7 0/2] fix ENOSPC issue of iobus dev Amos Kong
2012-03-09  4:17     ` [PATCH v7 1/2] KVM: resize kvm_io_range array dynamically Amos Kong
2012-03-09  4:17     ` [PATCH v7 2/2] KVM: set upper bounds for iobus dev to limit userspace Amos Kong
2012-03-09 21:07     ` [PATCH v7 0/2] fix ENOSPC issue of iobus dev Marcelo Tosatti

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=4F573F2F.4030103@redhat.com \
    --to=avi@redhat.com \
    --cc=akong@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --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.