From: Cornelia Huck <cohuck@redhat.com>
To: Pierre Morel <pmorel@linux.ibm.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
Collin Walling <walling@linux.ibm.com>,
thuth@redhat.com, david@redhat.com, qemu-devel@nongnu.org,
borntraeger@de.ibm.com, qemu-s390x@nongnu.org, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v2] s390x/pci: Set the iommu region size mpcifc request
Date: Wed, 16 Jan 2019 17:41:30 +0100 [thread overview]
Message-ID: <20190116174130.2ffb0713.cohuck@redhat.com> (raw)
In-Reply-To: <364e925b-4839-a10d-7a86-6a0bf229f4de@linux.ibm.com>
On Wed, 16 Jan 2019 16:44:09 +0100
Pierre Morel <pmorel@linux.ibm.com> wrote:
> On 16/01/2019 15:50, Halil Pasic wrote:
> > @Connie, will you add the Fixes tag? Do we need a cc stable (since
> > broken since 2016-06-19)?
> >
> > @Pierre: So you say it's a bug.
> > What can go wrong because of this?
> > For example if we interpret pal as a size, I guess we could end up with
> > the memory region not fitting the guest memory,
>
> The memory region will be too large compared with what the guest required.
Honestly, this does not look like QEMU stable material to me.
next prev parent reply other threads:[~2019-01-16 16:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 13:00 [Qemu-devel] [PATCH v2] s390x/pci: Set the iommu region size as guest wants Pierre Morel
2019-01-10 13:00 ` [Qemu-devel] [PATCH v2] s390x/pci: Set the iommu region size mpcifc request Pierre Morel
2019-01-15 13:59 ` Cornelia Huck
2019-01-15 15:35 ` Collin Walling
2019-01-16 12:40 ` Halil Pasic
2019-01-16 14:16 ` Pierre Morel
2019-01-16 14:34 ` Cornelia Huck
2019-01-16 14:50 ` Halil Pasic
2019-01-16 15:44 ` Pierre Morel
2019-01-16 16:41 ` Cornelia Huck [this message]
2019-01-17 15:13 ` Halil Pasic
2019-01-15 15:47 ` Cornelia Huck
2019-01-15 17:35 ` Pierre Morel
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=20190116174130.2ffb0713.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pmorel@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.com \
--cc=walling@linux.ibm.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).