public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Bruce Ashfield <bruce.ashfield@windriver.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Toshi Kani <toshi.kani@hpe.com>, Toshi Kani <toshi.kani@hp.com>,
	"Hart, Darren" <darren.hart@intel.com>,
	"saul.wold" <saul.wold@intel.com>,
	linux-kernel@vger.kernel.org, kvm ML <kvm@vger.kernel.org>,
	x86-ml <x86@kernel.org>
Subject: Re: runtime regression with "x86/mm/pat: Emulate PAT when it is disabled"
Date: Sat, 12 Mar 2016 13:03:03 +0100	[thread overview]
Message-ID: <20160312120303.GA23469@pd.tnic> (raw)
In-Reply-To: <1457738994.2804.266.camel@linuxfoundation.org>

On Fri, Mar 11, 2016 at 11:29:54PM +0000, Richard Purdie wrote:
> ... and if I remember rightly, the CPU features the kvm* options
> provide vary quite widely and wasn't consistent.

How so? Please elaborate so that we can fix those.

Btw, your reproducer works fine with -cpu kvm32 - only vncviewer's
window gets killed after a "Rect too large: 640x480 at (0, 0)" but
when I reconnect again right after it I see an X window asking me to
calibrate my touch screen and I'm at a loss as to where my touch screen
is... :-P

> Tweaking the kernel to only enable PAT with MTRR sounds like a good
> fix,

Yeah, the idea is to basically switch to uncacheable memtype as when
MTRRs are disabled.

-- 
Regards/Gruss,
    Boris.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
-- 

      reply	other threads:[~2016-03-12 12:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1457393912.15454.419.camel@hpe.com>
     [not found] ` <20160307235328.GD26051@windriver.com>
     [not found]   ` <1457398578.15454.421.camel@hpe.com>
     [not found]     ` <1457400913.15454.435.camel@hpe.com>
     [not found]       ` <20160310144250.GG23251@windriver.com>
     [not found]         ` <1457628591.15454.542.camel@hpe.com>
     [not found]           ` <20160310172029.GA2194@pd.tnic>
     [not found]             ` <20160310190429.GI23251@windriver.com>
     [not found]               ` <20160310191933.GC2194@pd.tnic>
     [not found]                 ` <20160311132356.43a7b373@lxorguk.ukuu.org.uk>
2016-03-11 13:40                   ` runtime regression with "x86/mm/pat: Emulate PAT when it is disabled" Borislav Petkov
2016-03-11 19:18                     ` Paolo Bonzini
2016-03-11 22:16                       ` Borislav Petkov
2016-03-11 22:28                         ` Bruce Ashfield
2016-03-11 23:29                           ` Richard Purdie
2016-03-12 12:03                             ` Borislav Petkov [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=20160312120303.GA23469@pd.tnic \
    --to=bp@suse.de \
    --cc=bruce.ashfield@windriver.com \
    --cc=darren.hart@intel.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=pbonzini@redhat.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=saul.wold@intel.com \
    --cc=toshi.kani@hp.com \
    --cc=toshi.kani@hpe.com \
    --cc=x86@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