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: Wed, 29 Jun 2022 10:04:19 -0400 [thread overview]
Message-ID: <20220629100152-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220629122050.yj7zp2xthtwmigzh@sirius.home.kraxel.org>
On Wed, Jun 29, 2022 at 02:20:50PM +0200, Gerd Hoffmann wrote:
> On Wed, Jun 29, 2022 at 03:16:17AM -0400, Michael S. Tsirkin wrote:
> > On Wed, Jun 29, 2022 at 09:10:23AM +0200, Gerd Hoffmann wrote:
> > > On Mon, Jun 27, 2022 at 06:37:50PM -0400, Michael S. Tsirkin wrote:
> > > > 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.
> > >
> > > Well, it is the *default* value which doesn't work on microvm.
> > >
> > > take care,
> > > Gerd
> >
> > Changing defaults is ok of course. Let's just not override the user.
>
> Ok, so I could use a compat property instead and change the default
> for microvm that way. That would allow the user set any value it
> wants.
And if you like check the value and fail init if not 0.
> I still don't see the point though. There is only a single value which
> makes sense on microvm. Which is zero. The only effect the user could
> archive is make the firmware throwing errors ...
>
> take care,
> Gerd
My concern is simple: if right now we override the value then
some users might set it to != 0 by mistake. Then if down the road
we want to intepret != 0 in some way, these setups
will start failing. I don't claim to see a use-case why we'd want to
but it's hard to predict the future with certainty.
--
MST
prev parent reply other threads:[~2022-06-29 14:08 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
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 [this message]
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=20220629100152-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 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).