All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yang, Sheng" <sheng.yang@intel.com>
To: kvm@vger.kernel.org
Cc: Alex Williamson <alex.williamson@hp.com>, Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH 4/4] kvm: bios: switch MTRRs to cover only the PCI range	and default to WB
Date: Sat, 27 Sep 2008 13:35:09 +0800	[thread overview]
Message-ID: <200809271335.10166.sheng.yang@intel.com> (raw)
In-Reply-To: <1222365149.8138.266.camel@2710p.home>

On Friday 26 September 2008 01:52:29 Alex Williamson wrote:
> kvm: bios: switch MTRRs to cover only the PCI range and default to WB
>
> This matches how some bare metal machines report MTRRs and avoids
> the problem of running out of MTRRs to cover all of RAM.
>
> Signed-off-by: Alex Williamson <alex.williamson@hp.com>
> ---
>
>  bios/rombios32.c |   24 ++++--------------------
>  1 files changed, 4 insertions(+), 20 deletions(-)
>
> diff --git a/bios/rombios32.c b/bios/rombios32.c
> index f8edf18..592abf9 100755
> --- a/bios/rombios32.c
> +++ b/bios/rombios32.c
> @@ -494,7 +494,6 @@ void setup_mtrr(void)
>          uint8_t valb[8];
>          uint64_t val;
>      } u;
> -    uint64_t vbase, vmask;
>
>      mtrr_cap = rdmsr(MSR_MTRRcap);
>      vcnt = mtrr_cap & 0xff;
> @@ -521,25 +520,10 @@ void setup_mtrr(void)
>      wrmsr_smp(MSR_MTRRfix4K_E8000, 0);
>      wrmsr_smp(MSR_MTRRfix4K_F0000, 0);
>      wrmsr_smp(MSR_MTRRfix4K_F8000, 0);
> -    vbase = 0;
> -    --vcnt; /* leave one mtrr for VRAM */
> -    for (i = 0; i < vcnt && vbase < ram_size; ++i) {
> -        vmask = (1ull << 40) - 1;
> -        while (vbase + vmask + 1 > ram_size)
> -            vmask >>= 1;
> -        wrmsr_smp(MTRRphysBase_MSR(i), vbase | 6);
> -        wrmsr_smp(MTRRphysMask_MSR(i), (~vmask & 0xfffffff000ull) |
> 0x800); -        vbase += vmask + 1;
> -    }
> -    for (vbase = 1ull << 32; i < vcnt && vbase < ram_end; ++i) {
> -        vmask = (1ull << 40) - 1;
> -        while (vbase + vmask + 1 > ram_end)
> -            vmask >>= 1;
> -        wrmsr_smp(MTRRphysBase_MSR(i), vbase | 6);
> -        wrmsr_smp(MTRRphysMask_MSR(i), (~vmask & 0xfffffff000ull) |
> 0x800); -        vbase += vmask + 1;
> -    }
> -    wrmsr_smp(MSR_MTRRdefType, 0xc00);
> +    /* Mark 3.5-4GB as UC, anything not specified defaults to WB */
> +    wrmsr_smp(MTRRphysBase_MSR(0), 0xe0000000ull | 0);
> +    wrmsr_smp(MTRRphysMask_MSR(0), ~(0x20000000ull - 1) | 0x800);
> +    wrmsr_smp(MSR_MTRRdefType, 0xc06);
>  }
>

I think we should do a little more than just write msr to update mtrr.

Intel SDM 10.11.8 "MTRR consideration in MP Systems" define the procedure to 
modify MTRR msr in MP. Especially, step 4 enter no-fill cache mode(set CR0.CD 
bit and clean NW bit), step 12 re-enabled the caching(clear this two bits).

We based on these behaviors to detect MTRR update.

(Forgot to raise the bug to Avi, recalled it now...)
--
regards
Yang, Sheng

  reply	other threads:[~2008-09-27  5:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-25 17:52 [PATCH 4/4] kvm: bios: switch MTRRs to cover only the PCI range and default to WB Alex Williamson
2008-09-27  5:35 ` Yang, Sheng [this message]
2008-09-27 13:36   ` Avi Kivity
2008-09-27 13:55     ` Zwane Mwaikambo
2008-09-28  1:58       ` Sheng Yang

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=200809271335.10166.sheng.yang@intel.com \
    --to=sheng.yang@intel.com \
    --cc=alex.williamson@hp.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.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 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.