All of lore.kernel.org
 help / color / mirror / Atom feed
From: Janusz <januszmk6@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Cc: edk2-devel@lists.01.org, guangrong.xiao@linux.intel.com
Subject: Re: [edk2] KVM: MTRR: fix memory type handling if MTRR is completely disabled
Date: Tue, 22 Sep 2015 12:29:46 +0200	[thread overview]
Message-ID: <56012D9A.4000607@gmail.com> (raw)
In-Reply-To: <5601186D.3000703@redhat.com>

W dniu 22.09.2015 o 10:59, Paolo Bonzini pisze:
>
> On 18/09/2015 11:37, Janusz wrote:
>> Hello,
>>
>> I am writting about this patch that was posted by Xiao:
>> http://www.spinics.net/lists/kvm/msg119044.html and this:
>> http://www.spinics.net/lists/kvm/msg119045.html
>> I've tested both kernel 4.2 and 4.3 and problem still exists when I use
>> OVMF - 100% cpu usage, VM resetting, while it works properly on kernel 4.1
> Is this an Intel or AMD CPU?
>
> Paolo
Intel i7 6700k

      reply	other threads:[~2015-09-22 10:29 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18  9:37 [edk2] KVM: MTRR: fix memory type handling if MTRR is completely disabled Janusz
2015-09-18 10:07 ` Laszlo Ersek
2015-09-18 17:48   ` Janusz
2015-09-21  2:51     ` Xiao Guangrong
2015-09-21  3:30       ` Wanpeng Li
2015-09-21  3:40         ` Xiao Guangrong
2015-10-01 14:12           ` Janusz
2015-10-01 14:18             ` Paolo Bonzini
2015-10-02 14:38               ` Janusz
2015-10-10 20:07                 ` Xiao Guangrong
2015-10-12 18:20                   ` Xiao Guangrong
2015-10-12 18:29                     ` Xiao Guangrong
2015-10-14  3:58                 ` Xiao Guangrong
2015-10-14  7:37                   ` Janusz
2015-10-14  8:24                     ` Xiao Guangrong
2015-10-14  8:32                       ` Xiao Guangrong
2015-10-14  9:13                         ` Janusz
2015-10-14  9:16                           ` Janusz
2015-10-14  9:47                         ` Laszlo Ersek
2015-10-15  3:59                           ` Xiao Guangrong
2015-10-14 18:08                         ` Janusz
2015-10-15  4:19                           ` Xiao Guangrong
2015-10-15  6:19                             ` Janusz
2015-10-15  6:41                               ` Xiao Guangrong
2015-10-15  6:58                                 ` Janusz
2015-10-15  7:10                                   ` Xiao Guangrong
2015-10-15  7:21                                     ` Janusz
2015-10-15 16:18                                     ` Laszlo Ersek
2015-10-15 16:53                                       ` Kinney, Michael D
2015-10-15 18:46                                         ` Laszlo Ersek
2015-10-20 17:27                                           ` Janusz
2015-10-20 17:44                                             ` Laszlo Ersek
2015-10-20 18:52                                               ` Janusz Mocek
     [not found]                                       ` <5620696F.7050406@linux.intel.com>
2015-10-16 18:22                                         ` Laszlo Ersek
2015-09-21  8:23       ` Janusz
2015-09-22  8:59 ` Paolo Bonzini
2015-09-22 10:29   ` Janusz [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=56012D9A.4000607@gmail.com \
    --to=januszmk6@gmail.com \
    --cc=edk2-devel@lists.01.org \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    /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.