From: Dan Williams <dan.j.williams@intel.com>
To: Kirill Shutemov <kirill.shutemov@linux.intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Cc: <dave.hansen@linux.intel.com>, <x86@kernel.org>,
Vishal Annapurve <vannapurve@google.com>,
Nikolay Borisov <nik.borisov@suse.com>, <stable@vger.kernel.org>,
<linux-coco@lists.linux.dev>
Subject: Re: [PATCH] x86/ioremap: Maintain consistent IORES_MAP_ENCRYPTED for BIOS data
Date: Wed, 2 Apr 2025 13:56:49 -0700 [thread overview]
Message-ID: <67eda491a62ac_1a6d9294ca@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <z7h6sepvvrqvmpiccqubganhshcbzzrbvda7dntzufqywei4gz@6clsg5lbvamd>
Kirill Shutemov wrote:
[..]
> > diff --git a/arch/x86/mm/ioremap.c b/arch/x86/mm/ioremap.c
> > index 42c90b420773..9e81286a631e 100644
> > --- a/arch/x86/mm/ioremap.c
> > +++ b/arch/x86/mm/ioremap.c
> > @@ -122,6 +122,10 @@ static void __ioremap_check_other(resource_size_t addr, struct ioremap_desc *des
> > return;
> > }
> >
> > + /* Ensure BIOS data (see devmem_is_allowed()) is consistently mapped */
> > + if (PHYS_PFN(addr) < 256)
>
> Maybe
> if (addr < BIOS_END)
>
> ?
Looks good to me.
prev parent reply other threads:[~2025-04-02 20:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 23:14 [PATCH] x86/ioremap: Maintain consistent IORES_MAP_ENCRYPTED for BIOS data Dan Williams
2025-04-01 5:57 ` Nikolay Borisov
2025-04-02 20:55 ` Dan Williams
2025-04-01 7:57 ` Kirill Shutemov
2025-04-01 15:07 ` Tom Lendacky
2025-04-01 17:59 ` Dave Hansen
2025-04-02 21:03 ` Dan Williams
2025-04-02 18:55 ` Naveen N Rao
2025-04-02 21:36 ` Dan Williams
2025-04-03 12:11 ` Naveen N Rao
2025-04-02 20:56 ` Dan Williams [this message]
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=67eda491a62ac_1a6d9294ca@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=nik.borisov@suse.com \
--cc=stable@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=vannapurve@google.com \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox