[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240904155203.GJ3915968@nvidia.com>
Date: Wed, 4 Sep 2024 12:52:03 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Jiaqi Yan <jiaqiyan@...gle.com>
Cc: Peter Xu <peterx@...hat.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Gavin Shan <gshan@...hat.com>,
Catalin Marinas <catalin.marinas@....com>, x86@...nel.org,
Ingo Molnar <mingo@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>,
Alistair Popple <apopple@...dia.com>, kvm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Sean Christopherson <seanjc@...gle.com>,
Oscar Salvador <osalvador@...e.de>, Borislav Petkov <bp@...en8.de>,
Zi Yan <ziy@...dia.com>, Axel Rasmussen <axelrasmussen@...gle.com>,
David Hildenbrand <david@...hat.com>,
Yan Zhao <yan.y.zhao@...el.com>, Will Deacon <will@...nel.org>,
Kefeng Wang <wangkefeng.wang@...wei.com>,
Alex Williamson <alex.williamson@...hat.com>, ankita@...dia.com
Subject: Re: [PATCH v2 00/19] mm: Support huge pfnmaps
On Thu, Aug 29, 2024 at 12:21:39PM -0700, Jiaqi Yan wrote:
> I think we still want to attempt to SIGBUS userspace, regardless of
> doing unmap_mapping_range or not.
IMHO we need to eliminate this path if we actually want to keep things
mapped.
There is no way to generate the SIGBUS without poking a 4k hole in the
1G page, as only that 4k should get SIGBUS, every other byte of the 1G
is clean.
Jason
Powered by blists - more mailing lists