public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@kernel.org
Subject: [Bug 196409] kvm_amd nested pagetable gpu passthrough performance oddities
Date: Wed, 26 Jul 2017 07:33:44 +0000	[thread overview]
Message-ID: <bug-196409-28872-tde73mlyYs@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196409-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=196409

Thomas (thbeck84@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |thbeck84@gmail.com

--- Comment #2 from Thomas (thbeck84@gmail.com) ---
Please look into this well documented issue, it makes the new AMD platform very
unattractive for advanced virtualization. 

This is very unfortunate because the nature of Ryzen (many cores, competitive
IPC, good value, inofficial ECC support) would be excellent for this.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2017-07-26  7:33 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 10:39 [Bug 196409] New: kvm_amd nested pagetable gpu passthrough performance oddities bugzilla-daemon
2017-07-20 18:53 ` [Bug 196409] " bugzilla-daemon
2017-07-26  7:33 ` bugzilla-daemon [this message]
2017-07-26  8:59 ` bugzilla-daemon
2017-07-26 13:52 ` bugzilla-daemon
2017-07-26 16:34 ` bugzilla-daemon
2017-07-27 10:40 ` bugzilla-daemon
2017-08-01  5:10 ` bugzilla-daemon
2017-08-18  6:48 ` bugzilla-daemon
2017-08-21 18:12 ` bugzilla-daemon
2017-08-25 14:33 ` bugzilla-daemon
2017-08-27 10:09 ` bugzilla-daemon
2017-08-27 15:58 ` bugzilla-daemon
2017-08-28 21:11 ` bugzilla-daemon
2017-08-30  8:36 ` bugzilla-daemon
2017-08-31 11:58 ` bugzilla-daemon
2017-09-01 13:50 ` bugzilla-daemon
2017-09-02  8:50 ` bugzilla-daemon
2017-09-02 18:44 ` bugzilla-daemon
2017-09-05 15:31 ` bugzilla-daemon
2017-09-08  9:58 ` bugzilla-daemon
2017-09-09  4:16 ` bugzilla-daemon
2017-09-13 20:57 ` bugzilla-daemon
2017-09-13 21:27 ` bugzilla-daemon
2017-09-15  7:30 ` bugzilla-daemon
2017-09-24  8:09 ` bugzilla-daemon
2017-09-24 10:43 ` bugzilla-daemon
2017-09-24 11:48 ` bugzilla-daemon
2017-09-24 12:25 ` bugzilla-daemon
2017-09-24 12:28 ` bugzilla-daemon
2017-09-24 12:59 ` bugzilla-daemon
2017-09-26 14:12 ` bugzilla-daemon
2017-10-09 10:19 ` bugzilla-daemon
2017-10-13 18:44 ` bugzilla-daemon
2017-10-24 23:42 ` bugzilla-daemon
2017-10-25 10:44 ` bugzilla-daemon
2017-10-25 18:46 ` bugzilla-daemon
2017-10-26 15:11 ` bugzilla-daemon
2017-10-27  8:34 ` bugzilla-daemon

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=bug-196409-28872-tde73mlyYs@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@kernel.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