From: Igor Mammedov <imammedo@redhat.com>
To: Ani Sinha <ani.sinha@nutanix.com>
Cc: Julia Suvorova <jusual@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Laine Stump <laine@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: Hot unplug disabling on pci-pci bridge
Date: Tue, 24 Mar 2020 15:09:35 +0100 [thread overview]
Message-ID: <20200324150935.4bfe8464@redhat.com> (raw)
In-Reply-To: <95F47446-8E5E-4CF1-A076-24D714F7A827@nutanix.com>
On Tue, 24 Mar 2020 11:49:53 +0000
Ani Sinha <ani.sinha@nutanix.com> wrote:
> > On Mar 24, 2020, at 4:38 PM, Igor Mammedov <imammedo@redhat.com> wrote:
> >
> > question is do you need to disable only unplug side both
> > (plug+unplug) operations (like we did with PCIE)?
>
> I need to disable the unplug side only.
I don't know about SHPC (i.e you probably can only have both or none)
For ACPI hotplug it should be possible to hack current impl.,
one would need to remove _EJ0->PCEJ methods.
That should hide ability to eject device in Windows but IO ports
will still be there so malicious guest will still be able to eject device.
But I'd emulate real hardware behavior where one would have plug+unplug
or none or disable acpi pci hotplug globally for VM.
>
> Ani
>
>
next prev parent reply other threads:[~2020-03-24 14:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 10:06 Hot unplug disabling on pci-pci bridge Ani Sinha
2020-03-24 11:08 ` Igor Mammedov
2020-03-24 11:49 ` Ani Sinha
2020-03-24 14:09 ` Igor Mammedov [this message]
2020-03-24 16:07 ` Ani Sinha
2020-03-24 11:17 ` Igor Mammedov
2020-03-24 13:29 ` Ani Sinha
2020-03-24 14:17 ` Igor Mammedov
2020-03-24 15:27 ` Ani Sinha
2020-04-17 15:33 ` Ani Sinha
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=20200324150935.4bfe8464@redhat.com \
--to=imammedo@redhat.com \
--cc=ani.sinha@nutanix.com \
--cc=jusual@redhat.com \
--cc=laine@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@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 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.