From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dely Sy <dely.l.sy@intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Rajat Jain <rajatxjain@gmail.com>,
Guenter Roeck <groeck@juniper.net>,
Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Praveen Kalamegham <praveen@nextio.com>
Subject: Re: Special handling of display/VGA devices in hotplug drivers
Date: Thu, 11 Dec 2014 22:57:18 +0000 [thread overview]
Message-ID: <20141211225718.403ada7e@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <CAErSpo4V8tYE+yHvQ+Se=tQHWAKafk89SmVTjeCVRzbA-VtQbg@mail.gmail.com>
> >> The PCI spec said that you were not allowed to hotplug VGA drivers.
> >> The big issue is that POST usually needs to run on those things, and
> >> there is no way to POST a PCI hotplugged device.
>
> I don't think this is a problem any more, is it? I think X can
> execute option ROMs, and if we assign the guest to a VM, the guest
> BIOS can also do it.
Providing the legacy I/O is routed to that device, it doesn't use DMA and
a few other things. X has been able to POST cards with vm86 or the 8086
emulator stuff for a long time (it had to in order to use most PC cards on
non x86 boxes).
Your bigger problem is the marvellous reliable way that X handles a GPU
simply vanishing, especially a legacy one.
Alan
prev parent reply other threads:[~2014-12-11 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 17:34 Bjorn Helgaas
2014-12-11 18:11 ` Greg Kroah-Hartman
2014-12-11 19:32 ` Jesse Barnes
2014-12-11 19:56 ` Guenter Roeck
2014-12-11 22:07 ` Bjorn Helgaas
2014-12-11 22:57 ` One Thousand Gnomes [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=20141211225718.403ada7e@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=bhelgaas@google.com \
--cc=dely.l.sy@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@juniper.net \
--cc=jbarnes@virtuousgeek.org \
--cc=kristen.c.accardi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=praveen@nextio.com \
--cc=rajatxjain@gmail.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
all inboxes | Powered by JetHome®