From: Amos Kong <akong@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: jasowang@redhat.com, alex.williamson@redhat.com,
kvm@vger.kernel.org, levinsasha928@gmail.com
Subject: Re: [PATCH v6 1/2] KVM: resize kvm_io_range array dynamically
Date: Fri, 09 Mar 2012 12:05:08 +0800 [thread overview]
Message-ID: <4F598174.9090405@redhat.com> (raw)
In-Reply-To: <20120308232022.GA24937@amt.cnet>
On 09/03/12 07:20, Marcelo Tosatti wrote:
> On Thu, Mar 08, 2012 at 10:03:55AM +0800, Amos Kong wrote:
>> This patch makes the kvm_io_range array can be resized dynamically.
>>
>> Signed-off-by: Amos Kong<akong@redhat.com>
>> ---
>> include/linux/kvm_host.h | 5 +++--
>> virt/kvm/kvm_main.c | 38 ++++++++++++++++++--------------------
>> 2 files changed, 21 insertions(+), 22 deletions(-)
>>
>> diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
>> index e42d85a..8a6c1a3 100644
>> --- a/include/linux/kvm_host.h
>> +++ b/include/linux/kvm_host.h
>> @@ -67,10 +67,11 @@ struct kvm_io_range {
>> struct kvm_io_device *dev;
>> };
>>
>> +#define NR_IOBUS_DEVS 300
>> +
>> 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 94e148e..f6ee1e2 100644
>> --- a/virt/kvm/kvm_main.c
>> +++ b/virt/kvm/kvm_main.c
>> @@ -2393,9 +2393,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,
>> @@ -2495,12 +2492,15 @@ 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)
>> return -ENOMEM;
>> + memcpy(new_bus, bus, sizeof(*bus) + (bus->dev_count *
>> + sizeof(struct kvm_io_range)));
>> kvm_io_bus_insert_dev(new_bus, dev, addr, len);
>> rcu_assign_pointer(kvm->buses[bus_idx], new_bus);
>> synchronize_srcu_expedited(&kvm->srcu);
>> @@ -2517,27 +2517,25 @@ 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) {
Hi Marcelo,
the deleted dev is found here.
>> 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 = kzalloc(sizeof(*bus) + ((bus->dev_count - 1) *
>> + sizeof(struct kvm_io_range)), GFP_KERNEL);
>> + if (!new_bus)
>> + return -ENOMEM;
>> +
>> + new_bus->dev_count--;
>
> Was just zeroed above?
>
>> + memcpy(new_bus->range, bus->range, i * sizeof(struct kvm_io_range));
Oh, dev_count memory needs to be copied.
memcpy(new_bus, bus, sizeof(*bus) + i * sizeof(struct
kvm_io_range));
new_bus->dev_count--;
>> + memcpy(new_bus->range + i, bus->range + i + 1,
>> + (new_bus->dev_count - i) * sizeof(struct kvm_io_range));
>
> Did you mean "i" as an indice for ->range[] ?
'i' is the index of deleted dev in bus->range[]
--
Amos.
next prev parent reply other threads:[~2012-03-09 3:54 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
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 [this message]
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=4F598174.9090405@redhat.com \
--to=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.