From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx@lists.freedesktop.org,
Alex Williamson <alex.williamson@redhat.com>,
Dave Airlie <airlied@redhat.com>
Subject: Re: [PATCH v2 1/1] drm/i915: Fix VGA handling using stop_machine() or mmio
Date: Mon, 30 Sep 2013 18:10:23 +0300 [thread overview]
Message-ID: <20130930151023.GD9395@intel.com> (raw)
In-Reply-To: <20130930145310.GK744@nuc-i3427.alporthouse.com>
On Mon, Sep 30, 2013 at 03:53:10PM +0100, Chris Wilson wrote:
> On Mon, Sep 30, 2013 at 05:41:44PM +0300, Ville Syrjälä wrote:
> > On Mon, Sep 30, 2013 at 03:24:37PM +0100, Chris Wilson wrote:
> > > On Mon, Sep 30, 2013 at 05:08:31PM +0300, ville.syrjala@linux.intel.com wrote:
> > > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > >
> > > > We have several problems with out VGA handling:
> > > > - We try to use the GMCH control VGA disable bit even though it may
> > > > be locked
> > > > - If we manage to disable VGA throuh GMCH control, we're no longer
> > > > able to correctly disable the VGA plane
> > > > - Taking part in the VGA arbitration is too expensive for X [1]
> > >
> > > I'd like to emphasize that X disables DRI if it detects 2 vga cards,
> > > effectively breaking all machines with a discrete GPU. Even if one of
> > > those is not being used.
> > >
> > > > +/*
> > > > + * 21 devices with 8 functions per device max on the same bus.
> > > > + * We don't need locking for these due to stop_machine().
> > > > + */
> > > > +static u16 vga_cmd[21*8];
> > > > +static u16 vga_ctl[21*8];
> > >
> > > Should we just allocate storage for when we need it? We are now adding
> > > several hundred bytes to our module, which is bound to cause us to use
> > > an extra page, and they can be passed around through the stop_machine
> > > closure rather than static.
> >
> > I guess we could do that. Although I do wonder a bit if we'd race with
> > hotplug. Not sure there's a way to hotplug stuff onto the root bus...
>
> Within stop-machine? I surely hope not!
Can we allocate there? I was thinking of allocating before stop_machine().
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2013-09-30 15:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 14:08 [PATCH 0/1] drm/i915: Another version of the vga stop_machine monstrosity ville.syrjala
2013-09-30 14:08 ` [PATCH v2 1/1] drm/i915: Fix VGA handling using stop_machine() or mmio ville.syrjala
2013-09-30 14:24 ` Chris Wilson
2013-09-30 14:41 ` Ville Syrjälä
2013-09-30 14:53 ` Chris Wilson
2013-09-30 15:10 ` Ville Syrjälä [this message]
2013-09-30 16:45 ` Chris Wilson
2013-09-30 18:37 ` Alex Williamson
2013-10-07 0:23 ` Dave Airlie
2013-10-07 7:34 ` Daniel Vetter
2013-10-02 13:42 ` [PATCH v3] " ville.syrjala
2013-10-07 9:15 ` Chris Wilson
2013-10-07 9:25 ` Ville Syrjälä
2013-10-07 9:44 ` Chris Wilson
2013-09-30 14:43 ` [PATCH v2 1/1] " Alex Williamson
2013-09-30 15:09 ` Ville Syrjälä
2013-09-30 16:45 ` Alex Williamson
2013-09-30 17:23 ` Ville Syrjälä
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=20130930151023.GD9395@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=airlied@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox