qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Gerd Hoffmann <kraxel@redhat.com>
Cc: David Gibson <dgibson@redhat.com>,
	Alexey Kardashevskiy <aik@au1.ibm.com>,
	qemu-devel@nongnu.org, Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 0/3] vga: add endianness switching support
Date: Tue, 23 Sep 2014 22:33:29 +0200	[thread overview]
Message-ID: <5421D919.8080209@suse.de> (raw)
In-Reply-To: <1411503873.4184.24.camel@pasglop>



On 23.09.14 22:24, Benjamin Herrenschmidt wrote:
> On Tue, 2014-09-23 at 14:30 +0200, Gerd Hoffmann wrote:
>>   Hi,
> 
> (Adding Mike)
> 
>> Series applies on top of the vga patches posted yesterday.
>> It adds a mmio register to the pci stdvga cards allowing
>> to switch framebuffer endiannness.  Ben's patches 1+2 prepare
>> for runtime-swicthable endianness and patch #3 actually
>> implements the new register.  It has been placed in a new
>> range to avoid conflicts in case the bochs dispi interface
>> will be extended in the future.  The separate range also
>> makes it easier to turn off on old machine types.
> 
> Thanks. I'll try to produce patches for offb and bochsdrmfb to
> adjust endianness & test some time this week or next week.
> 
> Now the remaining point of contention is the "auto switch"
> functionality which, sadly, is needed for existing LE guests to work
> properly.
> 
> I understand the reticence, on the other hand, our "pseries" machine is
> really a paravirtualized environment where qemu implements the
> hypervisor hcall interface, so in that context, it does make some sense
> that the "hypervisor" affects some HW configuration/state on endian
> switch (which is such an hcall).
> 
> The problem is how to do that in a reasonably clean way from an
> implementation perspective.
> 
> The patch at
> https://github.com/ozbenh/qemu/commit/778c92cebcd12fdafd2050dc4d7ca2521c462e46 is one attempt to do it, for whatever it's worth, but I'm open to alternatives.

Apart from stylistic problems I think the approach is reasonable. The
only alternative I could think of would be to simply loop through every
device in the device tree we can find and search for VGA objects.


Alex

      reply	other threads:[~2014-09-23 20:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23 12:30 [Qemu-devel] [PATCH 0/3] vga: add endianness switching support Gerd Hoffmann
2014-09-23 12:30 ` [Qemu-devel] [PATCH 1/3] vga: Make fb endian a common state variable Gerd Hoffmann
2014-09-26  4:28   ` David Gibson
2014-09-23 12:30 ` [Qemu-devel] [PATCH 2/3] vga: Add endian control register Gerd Hoffmann
2014-09-26  4:34   ` David Gibson
2014-09-23 12:30 ` [Qemu-devel] [PATCH 3/3] vga-pci: add qext region to mmio Gerd Hoffmann
2014-09-26  4:38   ` David Gibson
2014-09-29 16:18   ` Michael S. Tsirkin
2014-09-30 11:02     ` Gerd Hoffmann
2014-09-23 20:24 ` [Qemu-devel] [PATCH 0/3] vga: add endianness switching support Benjamin Herrenschmidt
2014-09-23 20:33   ` Alexander Graf [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=5421D919.8080209@suse.de \
    --to=agraf@suse.de \
    --cc=aik@au1.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=dgibson@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=mdroth@linux.vnet.ibm.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 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).