All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gordan Bobic <gordan@bobich.net>
To: Peter Kay <syllopsium@syllopsium.co.uk>
Cc: xen-devel@lists.xen.org
Subject: Re: AMD GPU passthrough in Xen
Date: Mon, 22 Sep 2014 16:05:41 +0100	[thread overview]
Message-ID: <54203AC5.2050102@bobich.net> (raw)
In-Reply-To: <2d24af6e-f1ec-4407-8f62-1493f9b49891@email.android.com>

On 09/22/2014 03:31 PM, Peter Kay wrote:
>
>
> On 22 September 2014 13:38:28 BST, Sander Eikelenboom <linux@eikelenboom.it> wrote:
>
>> Another interesting question/aspect would be qemu-traditional (with
>> rombios) or
>> "upstream" (with seabios) ?
> Point, although I didn't think this was generally an option in 4.2?
>
> Certainly I've found upstream to be functional (using a Quadro), but a less stable domU overall

Do you happen to know if the recent KVM/QEMU provides a feature to limit 
the amount of memory below 4GB to assign to the guest? Or provide a 
custom e820 map? To work around a hardware bug I have to somehow make 
sure that everything between 2.5GB and 4GB is reserved and untouchable.

Gordan

  reply	other threads:[~2014-09-22 15:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 12:16 AMD GPU passthrough in Xen Peter Kay
2014-09-22 12:38 ` Sander Eikelenboom
2014-09-22 14:31   ` Peter Kay
2014-09-22 15:05     ` Gordan Bobic [this message]
2014-09-23 11:22       ` Peter Kay
2014-09-23 13:19   ` Zytaruk, Kelly
2014-09-23 13:45     ` Sander Eikelenboom
2014-09-23 14:44       ` Gordan Bobic
2014-09-24 12:12       ` Zytaruk, Kelly
2014-09-24 12:56         ` Gordan Bobic
2014-09-24 13:31           ` Zytaruk, Kelly
2014-09-24 13:35             ` Gordan Bobic
2014-09-24 13:21         ` Sander Eikelenboom
2014-09-24 13:58           ` Zytaruk, Kelly
2014-09-24 14:16             ` Sander Eikelenboom
2014-09-24 15:10               ` Zytaruk, Kelly
2014-09-24 15:35                 ` Sander Eikelenboom

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=54203AC5.2050102@bobich.net \
    --to=gordan@bobich.net \
    --cc=syllopsium@syllopsium.co.uk \
    --cc=xen-devel@lists.xen.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.