Re: Problem with pat_enable() and commit 72cbc8f04fe2

2023-01-10 Thread Juergen Gross
On 10.01.23 10:38, Jan Beulich wrote: On 10.01.2023 06:59, Juergen Gross wrote: On 10.01.23 06:47, Juergen Gross wrote: On 09.01.23 19:28, Michael Kelley (LINUX) wrote: I've come across a case with a VM running on Hyper-V that doesn't get MTRRs, but the PAT is functional.  (This is a Confident

Re: Problem with pat_enable() and commit 72cbc8f04fe2

2023-01-10 Thread Jan Beulich
On 10.01.2023 06:59, Juergen Gross wrote: > On 10.01.23 06:47, Juergen Gross wrote: >> On 09.01.23 19:28, Michael Kelley (LINUX) wrote: >>> I've come across a case with a VM running on Hyper-V that doesn't get >>> MTRRs, but the PAT is functional.  (This is a Confidential VM using >>> AMD's SEV-SNP

Re: Problem with pat_enable() and commit 72cbc8f04fe2

2023-01-09 Thread Juergen Gross
On 10.01.23 06:47, Juergen Gross wrote: On 09.01.23 19:28, Michael Kelley (LINUX) wrote: I've come across a case with a VM running on Hyper-V that doesn't get MTRRs, but the PAT is functional.  (This is a Confidential VM using AMD's SEV-SNP encryption technology with the vTOM option.)  In this c

Re: Problem with pat_enable() and commit 72cbc8f04fe2

2023-01-09 Thread Juergen Gross
On 09.01.23 19:28, Michael Kelley (LINUX) wrote: I've come across a case with a VM running on Hyper-V that doesn't get MTRRs, but the PAT is functional. (This is a Confidential VM using AMD's SEV-SNP encryption technology with the vTOM option.) In this case, the changes in commit 72cbc8f04fe2 (