From: Lukas Wunner <lukas@wunner.de>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org
Subject: Re: PCI resource allocation mismatch with BIOS
Date: Tue, 29 Nov 2022 17:06:26 +0100 [thread overview]
Message-ID: <20221129160626.GA19822@wunner.de> (raw)
In-Reply-To: <20221129084646.0b22c80b.alex.williamson@redhat.com>
On Tue, Nov 29, 2022 at 08:46:46AM -0700, Alex Williamson wrote:
> Maybe the elephant in the room is why it's apparently such common
> practice to need to perform a hard reset these devices outside of
> virtualization scenarios...
These GPUs are used as accelerators in cloud environments.
They're reset to a pristine state when handed out to another tenant
to avoid info leaks from the previous tenant.
That should be a legitimate usage of PCIe reset, no?
Thanks,
Lukas
next prev parent reply other threads:[~2022-11-29 16:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 11:14 PCI resource allocation mismatch with BIOS Mika Westerberg
2022-11-28 20:39 ` Bjorn Helgaas
2022-11-28 22:06 ` Alex Williamson
2022-11-29 6:48 ` Lukas Wunner
2022-11-29 10:09 ` Mika Westerberg
2022-11-29 13:52 ` Alex Williamson
2022-11-29 15:07 ` Mika Westerberg
2022-11-29 15:46 ` Alex Williamson
2022-11-29 16:06 ` Lukas Wunner [this message]
2022-11-29 16:12 ` Alex Williamson
2022-11-30 7:43 ` Lukas Wunner
2022-11-30 7:57 ` Mika Westerberg
2022-11-30 15:47 ` Alex Williamson
2022-12-01 9:41 ` Mika Westerberg
2022-12-09 11:08 ` Mika Westerberg
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=20221129160626.GA19822@wunner.de \
--to=lukas@wunner.de \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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