From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Sergio Lopez <slp@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Eduardo Habkost <eduardo@habkost.net>
Subject: Re: [PATCH] microvm: turn off io reservations for pcie root ports
Date: Mon, 27 Jun 2022 18:37:50 -0400 [thread overview]
Message-ID: <20220627183724-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220609072838.jcq4cdofpwvlew7j@sirius.home.kraxel.org>
On Thu, Jun 09, 2022 at 09:28:38AM +0200, Gerd Hoffmann wrote:
> On Wed, Jun 08, 2022 at 12:06:17PM -0400, Michael S. Tsirkin wrote:
> > On Fri, Jun 03, 2022 at 10:59:20AM +0200, Gerd Hoffmann wrote:
> > > The pcie host bridge has no io window on microvm,
> > > so io reservations will not work.
> > >
> > > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> >
> > I don't much like overriding user like this. We end up users
> > setting it to silly values and then if we do want to
> > support this things just break. Thoughts?
>
> Well, it just looked like the simplest way to tell the firmware that
> io reservations are pointless. Do you have a better idea?
>
> take care,
> Gerd
Fail if user supplies values we can't support.
--
MST
next prev parent reply other threads:[~2022-06-27 22:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 8:59 [PATCH] microvm: turn off io reservations for pcie root ports Gerd Hoffmann
2022-06-04 13:25 ` Philippe Mathieu-Daudé via
2022-06-06 5:08 ` Sergio Lopez
2022-06-08 16:06 ` Michael S. Tsirkin
2022-06-09 7:28 ` Gerd Hoffmann
2022-06-27 22:37 ` Michael S. Tsirkin [this message]
2022-06-29 7:10 ` Gerd Hoffmann
2022-06-29 7:16 ` Michael S. Tsirkin
2022-06-29 12:20 ` Gerd Hoffmann
2022-06-29 14:04 ` Michael S. Tsirkin
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=20220627183724-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eduardo@habkost.net \
--cc=kraxel@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=slp@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.