Messages in this thread | | | Date | Wed, 15 Feb 2023 09:25:13 +0100 | From | Juergen Gross <> | Subject | Re: [PATCH v2 0/8] x86/mtrr: fix handling with PAT but without MTRR |
| |
On 13.02.23 19:21, Edgecombe, Rick P wrote: > On Mon, 2023-02-13 at 07:12 +0100, Juergen Gross wrote: >> >> Thanks for the report. >> >> I'll have a look. Probably I'll need to re-add the check for WB in >> patch 7. > > Sure, let me know if you need any more details about by setup.
I have reproduced the issue.
Adding back the test for WB will fix it, but I'm not sure this is really what I should do.
The problem arises in case a large mapping is spanning multiple MTRRs, even if they define the same caching type (uniform is set to 0 in this case).
So the basic question for me is: shouldn't the semantics of uniform be adpated? Today it means "the range is covered by only one MTRR or by none". Looking at the use cases I'm wondering whether it shouldn't be "the whole range has the same caching type".
Thoughts?
Juergen [unhandled content-type:application/pgp-keys][unhandled content-type:application/pgp-signature] | |