From: Marcelo Tosatti <mtosatti@redhat.com>
To: Amos Kong <akong@redhat.com>
Cc: jasowang@redhat.com, alex.williamson@redhat.com,
kvm@vger.kernel.org, levinsasha928@gmail.com
Subject: Re: [PATCH v7 0/2] fix ENOSPC issue of iobus dev
Date: Fri, 9 Mar 2012 18:07:01 -0300 [thread overview]
Message-ID: <20120309210701.GA23182@amt.cnet> (raw)
In-Reply-To: <20120309041003.3901.63690.stgit@dhcp-8-167.nay.redhat.com>
On Fri, Mar 09, 2012 at 12:17:22PM +0800, Amos Kong wrote:
> Boot up qemu-kvm guest with 232 multiple functions disks, qemu
> will report a ENOSPC error, it's not good to statically increase
> iobus array. This patchset makes kvm_io_range array can be
> resized dynamically, and change dev limit to 1000.
>
> Changes from v1:
> - fix typo: kvm_io_bus_range -> kvm_io_range
>
> Changes from v2:
> - unregister device only when it exists
>
> Changes from v3:
> - set upper bounds to limit userspace
>
> Changes from v4:
> - check if allocate successfully before memcpy()
> - separate the change to 1000 devs to a new patch
>
> Changes from v5:
> - memcpy() two times, drop sort
>
> Changes from V6:
> - copy bus->dev_count memory to new_bus
>
> ---
>
> Amos Kong (2):
> KVM: resize kvm_io_range array dynamically
> KVM: set upper bounds for iobus dev to limit userspace
Applied, thanks.
prev parent reply other threads:[~2012-03-09 21:09 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
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 ` Marcelo Tosatti [this message]
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=20120309210701.GA23182@amt.cnet \
--to=mtosatti@redhat.com \
--cc=akong@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.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).