[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<MW4PR12MB72138D289232B5D62078158DB04B2@MW4PR12MB7213.namprd12.prod.outlook.com>
Date: Fri, 9 Feb 2024 14:10:51 +0000
From: Ankit Agrawal <ankita@...dia.com>
To: Oliver Upton <oliver.upton@...ux.dev>, Catalin Marinas
<catalin.marinas@....com>
CC: Jason Gunthorpe <jgg@...dia.com>, "maz@...nel.org" <maz@...nel.org>,
"james.morse@....com" <james.morse@....com>, "suzuki.poulose@....com"
<suzuki.poulose@....com>, "yuzenghui@...wei.com" <yuzenghui@...wei.com>,
"reinette.chatre@...el.com" <reinette.chatre@...el.com>, "surenb@...gle.com"
<surenb@...gle.com>, "stefanha@...hat.com" <stefanha@...hat.com>,
"brauner@...nel.org" <brauner@...nel.org>, "will@...nel.org"
<will@...nel.org>, "mark.rutland@....com" <mark.rutland@....com>,
"alex.williamson@...hat.com" <alex.williamson@...hat.com>,
"kevin.tian@...el.com" <kevin.tian@...el.com>, "yi.l.liu@...el.com"
<yi.l.liu@...el.com>, "ardb@...nel.org" <ardb@...nel.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"andreyknvl@...il.com" <andreyknvl@...il.com>, "wangjinchao@...sion.com"
<wangjinchao@...sion.com>, "gshan@...hat.com" <gshan@...hat.com>,
"ricarkol@...gle.com" <ricarkol@...gle.com>, "linux-mm@...ck.org"
<linux-mm@...ck.org>, "lpieralisi@...nel.org" <lpieralisi@...nel.org>,
"rananta@...gle.com" <rananta@...gle.com>, "ryan.roberts@....com"
<ryan.roberts@....com>, Aniket Agashe <aniketa@...dia.com>, Neo Jia
<cjia@...dia.com>, Kirti Wankhede <kwankhede@...dia.com>, "Tarun Gupta
(SW-GPU)" <targupta@...dia.com>, Vikram Sethi <vsethi@...dia.com>, Andy
Currid <acurrid@...dia.com>, Alistair Popple <apopple@...dia.com>, John
Hubbard <jhubbard@...dia.com>, Dan Williams <danw@...dia.com>,
"kvmarm@...ts.linux.dev" <kvmarm@...ts.linux.dev>, Matt Ochs
<mochs@...dia.com>, Zhi Wang <zhiw@...dia.com>, "kvm@...r.kernel.org"
<kvm@...r.kernel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v6 1/4] kvm: arm64: introduce new flag for non-cacheable
IO memory
>> + default:
>> + WARN_ON_ONCE(1);
>
> Return -EINVAL?
Sure.
>> > + case KVM_PGTABLE_PROT_NORMAL_NC:
>> > + attr = KVM_S2_MEMATTR(pgt, NORMAL_NC);
>> > + break;
>>
>> Does it make sense to allow executable here as well? I don't think it's
>> harmful but not sure there's a use-case for it either.
>
> Ah, we should just return EINVAL for that too.
>
> I get that the memory attribute itself is not problematic, but since
> we're only using this thing for MMIO it'd be a rather massive
> bug in KVM... We reject attempts to do this earlier in user_mem_abort().
Ack, will change to test executable and return -EINVAL in that case.
Powered by blists - more mailing lists