From: Tomasz Wroblewski <tomasz.wroblewski@gmail.com>
To: Jan Beulich <JBeulich@suse.com>, Tim Deegan <tim@xen.org>
Cc: xen-devel@lists.xenproject.org
Subject: Re: GPU passthrough performance regression in >4GB vms due to XSA-60 changes
Date: Mon, 19 May 2014 17:48:02 +0200 [thread overview]
Message-ID: <537A27B2.5010404@gmail.com> (raw)
In-Reply-To: <537A3E650200007800013C04@mail.emea.novell.com>
On 05/19/2014 05:24 PM, Jan Beulich wrote:
>>>> On 19.05.14 at 16:20, <tomasz.wroblewski@gmail.com> wrote:
>> On 05/19/2014 02:44 PM, Jan Beulich wrote:
>>> I used plural for a reason - I'm afraid you would need to start out with
>>> taking them all, and then possibly determine which ones to drop as
>>> being unrelated to the issue at hand.
>> Looks like a partial backport of your commit
>>
>> commit aa9114edd97b292cd89b3616e3f2089471fd2201
>> Author: Jan Beulich <jbeulich@suse.com>
>> Date: Thu Apr 10 16:01:41 2014 +0200
>>
>> x86/EPT: force re-evaluation of memory type as necessary
>>
>> is all that's necessary. Attaching it versus 4.3.2. I only left the
>> memory_type_change calls in MTRR related areas, since only this is
>> problematic for the particular issue. This is probably good enough for
>> us, thanks for the pointers! Do you think this one is a relatively safe
>> for the stable branches?
> I'm rather reluctant to put in any half-baked stuff like this - in going
> through the set of changes you certainly noticed that there are
> quite a few more fixes, that all deal with similar problems. So the
> partial (and amended) backport you provided is really of the sort
> "my problem is fixed, let's ignore everything else"...
Yup. Backporting the smallest viable fix seems ok solution for us, so I
did it and we'll test it a bit, but I fully agree it's likely not the
best thing for upstream project especially since that code seems very
fresh. Given there doesn't seem to be much noise about recent (and very
obvious) vm performance regressions with pci passthrough and large
amounts of memory, it might be quite an unpopular use case to justify
the risky backport.
> Independently of this - Tim, do you think this EPT misconfig stuff can
> already be considered mature enough for backporting? It's been in a
> little over a month, and considering that we're using formally
> undefined behavior here, I'd rather view this as not yet a backport
> candidate.
>
> Jan
>
next prev parent reply other threads:[~2014-05-19 15:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 9:11 GPU passthrough performance regression in >4GB vms due to XSA-60 changes Tomasz Wroblewski
2014-05-15 12:32 ` Jan Beulich
2014-05-15 12:10 ` Tomasz Wroblewski
2014-05-15 13:23 ` Jan Beulich
2014-05-15 13:39 ` Tomasz Wroblewski
2014-05-15 14:34 ` Tomasz Wroblewski
2014-05-15 14:56 ` Tomasz Wroblewski
2014-05-15 16:07 ` Jan Beulich
2014-05-15 15:39 ` Tomasz Wroblewski
2014-05-16 6:33 ` Jan Beulich
2014-05-16 11:18 ` Tomasz Wroblewski
2014-05-16 11:38 ` Jan Beulich
2014-05-16 14:36 ` Jan Beulich
2014-05-19 10:29 ` Tomasz Wroblewski
2014-05-19 10:38 ` Jan Beulich
2014-05-19 10:47 ` Tomasz Wroblewski
2014-05-19 11:07 ` Jan Beulich
2014-05-19 11:32 ` Tomasz Wroblewski
2014-05-19 12:06 ` Jan Beulich
2014-05-19 12:17 ` Tomasz Wroblewski
2014-05-19 12:44 ` Jan Beulich
2014-05-19 14:20 ` Tomasz Wroblewski
2014-05-19 15:24 ` Jan Beulich
2014-05-19 15:48 ` Tomasz Wroblewski [this message]
2014-05-19 17:36 ` Tim Deegan
2014-05-20 6:31 ` Jan Beulich
2014-05-19 10:42 ` Tomasz Wroblewski
2014-05-19 11:01 ` Jan Beulich
2014-05-19 11:09 ` Tomasz Wroblewski
2014-05-19 11:19 ` Jan Beulich
2014-05-15 16:01 ` Jan Beulich
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=537A27B2.5010404@gmail.com \
--to=tomasz.wroblewski@gmail.com \
--cc=JBeulich@suse.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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).