qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: linux-s390@vger.kernel.org, kvm@vger.kernel.org, gleb@kernel.org,
	qemu-devel@nongnu.org, agraf@suse.de, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 3/5] KVM: s390: adapter interrupt sources
Date: Fri, 21 Mar 2014 11:07:13 +0100	[thread overview]
Message-ID: <20140321110713.4b2b29e8.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <532C05CB.5010604@de.ibm.com>

On Fri, 21 Mar 2014 10:26:35 +0100
Christian Borntraeger <borntraeger@de.ibm.com> wrote:

> On 17/03/14 19:11, Cornelia Huck wrote:
> > Add a new interface to register/deregister sources of adapter interrupts
> > identified by an unique id via the flic. Adapters may also be maskable
> > and carry a list of pinned pages.
> > 
> > These adapters will be used by irq routing later.
> > 
> > Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> 
> [...]
> 
> > +static int kvm_s390_adapter_map(struct kvm *kvm, unsigned int id, __u64 addr)
> > +{
> > +	struct s390_io_adapter *adapter = get_io_adapter(kvm, id);
> > +	struct s390_map_info *map;
> > +	int ret;
> > +
> > +	if (!adapter || !addr)
> > +		return -EINVAL;
> > +
> > +	map = kzalloc(sizeof(*map), GFP_KERNEL);
> > +	if (!map) {
> > +		ret = -ENOMEM;
> > +		goto out;
> > +	}
> > +	INIT_LIST_HEAD(&map->list);
> > +	map->addr = addr;
> > +	ret = get_user_pages_fast(addr, 1, 1, &map->page);
> > +	if (ret < 0)
> > +		goto out;
> > +	BUG_ON(ret != 1);
> > +	down_write(&adapter->maps_lock);
> > +	list_add_tail(&map->list, &adapter->maps);
> > +	up_write(&adapter->maps_lock);
> > +	ret = 0;
> 
> Can you limit the amount of pinned pages to something sane, e.g. 1MB?
> As far as I can see, QEMU will fall back to non-irqfd if the mapping fails.

I'll introduce a counter for that.

> 
> Otherwise looks good.
> 
> Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
> 

  reply	other threads:[~2014-03-21 10:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17 18:11 [Qemu-devel] [PATCH v2 0/5] KVM: irqfds for s390 Cornelia Huck
2014-03-17 18:11 ` [Qemu-devel] [PATCH v2 1/5] KVM: eventfd: Fix lock order inversion Cornelia Huck
2014-03-17 21:55   ` Christian Borntraeger
2014-03-18  9:18     ` Cornelia Huck
2014-03-18 16:05     ` Paolo Bonzini
2014-03-17 18:11 ` [Qemu-devel] [PATCH v2 2/5] KVM: Add per-vm capability enablement Cornelia Huck
2014-03-17 22:09   ` Christian Borntraeger
2014-03-21  9:12   ` Christian Borntraeger
2014-03-17 18:11 ` [Qemu-devel] [PATCH v2 3/5] KVM: s390: adapter interrupt sources Cornelia Huck
2014-03-18  8:11   ` Heiko Carstens
2014-03-18  8:41     ` Cornelia Huck
2014-03-21  9:26   ` Christian Borntraeger
2014-03-21 10:07     ` Cornelia Huck [this message]
2014-03-17 18:11 ` [Qemu-devel] [PATCH v2 4/5] KVM: s390: irq routing for adapter interrupts Cornelia Huck
2014-03-21  9:32   ` Christian Borntraeger
2014-03-21 10:08     ` Cornelia Huck
2014-03-17 18:11 ` [Qemu-devel] [PATCH v2 5/5] KVM: Bump KVM_MAX_IRQ_ROUTES for s390 Cornelia Huck
2014-03-18 16:07   ` Paolo Bonzini

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=20140321110713.4b2b29e8.cornelia.huck@de.ibm.com \
    --to=cornelia.huck@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=gleb@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).