All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Amos Kong <akong@redhat.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"jasowang@redhat.com" <jasowang@redhat.com>,
	"mtosatti@redhat.com" <mtosatti@redhat.com>,
	alex williamson <alex.williamson@redhat.com>,
	"avi@redhat.com" <avi@redhat.com>,
	"levinsasha928@gmail.com" <levinsasha928@gmail.com>
Subject: Re: [PATCH v3] KVM: Resize kvm_io_range array dynamically
Date: Wed, 29 Feb 2012 16:29:33 +0100	[thread overview]
Message-ID: <4F4E445D.8090104@siemens.com> (raw)
In-Reply-To: <01ed65cf-7783-4888-93b7-3d5e2cceadc6@zmail13.collab.prod.int.phx2.redhat.com>

On 2012-02-29 16:22, Amos Kong wrote:
> ----- Original Message -----
>> On 2012-02-29 14:30, 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. The maximum of coalesced mmio zone is 100,
>>> each zone has an iobus devices. 300 io_bus devices is not enough.
>>>
>>> This patch makes the kvm_io_range array can be resized dynamically.
>>
>> Is there any limit, or can userspace allocate arbitrary amounts of
>> kernel memory this way?
> 
> Hi Jan,
> 
> There is a fixed array in linux-2.6/include/linux/kvm_host.h,
> we can only register 300 devices.
> 
> struct kvm_io_range {
>         gpa_t addr;               
>         int len;
>         struct kvm_io_device *dev;
> };
> 
> struct kvm_io_bus {
>         int                   dev_count;
> #define NR_IOBUS_DEVS 300
>         struct kvm_io_range range[NR_IOBUS_DEVS];
> };
>                                   ^^^^^^^^^^^^^^

Right. But doesn't your patch remove precisely this limit? So what
limits userspace now? To register 300 million devices...?

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2012-02-29 15:29 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 [this message]
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     ` [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=4F4E445D.8090104@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=akong@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=avi@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.