From: Halil Pasic <pasic@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
Tony Krowiak <akrowiak@linux.ibm.com>,
Pierre Morel <pmorel@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC] vfio-ap: flag as compatible with balloon
Date: Fri, 7 Dec 2018 13:52:53 +0100 [thread overview]
Message-ID: <20181207135253.10e3e021@oc2783563651> (raw)
In-Reply-To: <20181207132946.00df1f5a.cohuck@redhat.com>
On Fri, 7 Dec 2018 13:29:46 +0100
Cornelia Huck <cohuck@redhat.com> wrote:
> On Fri, 7 Dec 2018 13:17:02 +0100
> Christian Borntraeger <borntraeger@de.ibm.com> wrote:
>
> > On 05.12.2018 15:51, Cornelia Huck wrote:
> > > vfio-ap devices do not pin any pages in the host. Therefore, they
> > > are belived to be compatible with memory ballooning.
> > >
> > > Flag them as compatible, so both vfio-ap and a balloon can be
> > > used simultaneously.
> > >
> > > Signed-off-by: Cornelia Huck <cohuck@redhat.com>
With the comment stuff sorted out:
Reviewed-by: Halil Pasic <pasic@linux.ibm.com>
@Connie: Just had a look at the MAINTAINERS file and hw/vfio/ap.c
is listed under Arch. support S90 with you as a maintainer, and under
vfio-ap with 4 maintainers listed one of them being me. The question
is who is going to post a PULL request for this?
> >
> > Does it make sense to add cc stable for 3.1?
>
> Can do that, given that s390x systems really rely on the ballooner in
> general.
>
I agree with cc stable.
Halil
next prev parent reply other threads:[~2018-12-07 12:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 14:51 [Qemu-devel] [PATCH RFC] vfio-ap: flag as compatible with balloon Cornelia Huck
2018-12-05 16:05 ` Christian Borntraeger
2018-12-05 16:38 ` David Hildenbrand
2018-12-05 16:45 ` Cornelia Huck
2018-12-05 17:25 ` Christian Borntraeger
2018-12-06 8:28 ` David Hildenbrand
2018-12-06 12:32 ` Halil Pasic
2018-12-06 12:48 ` Cornelia Huck
2018-12-06 20:51 ` Tony Krowiak
2018-12-06 23:01 ` Tony Krowiak
2018-12-07 12:17 ` Christian Borntraeger
2018-12-07 12:29 ` Cornelia Huck
2018-12-07 12:32 ` Christian Borntraeger
2018-12-07 12:38 ` Cornelia Huck
2018-12-07 12:52 ` Halil Pasic [this message]
2018-12-07 13:17 ` Cornelia Huck
2018-12-07 14:04 ` Halil Pasic
2018-12-07 15:00 ` Cornelia Huck
2018-12-07 15:05 ` Cornelia Huck
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=20181207135253.10e3e021@oc2783563651 \
--to=pasic@linux.ibm.com \
--cc=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=pmorel@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@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).