From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Daniel Borkmann <daniel@iogearbox.net>,
bpf <bpf@vger.kernel.org>, Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org
Subject: Re: vm_area at addr ffffffffc0800000 is not marked as VM_IOREMAP
Date: Fri, 8 Mar 2024 08:37:40 -0800 [thread overview]
Message-ID: <CAADnVQJ=_HwPo=Cnemwd095dcsLXKtp=VVBB4bG9_ovfwG8bWw@mail.gmail.com> (raw)
In-Reply-To: <20240308161331.GA682898@bhelgaas>
On Fri, Mar 8, 2024 at 8:13 AM Bjorn Helgaas <helgaas@kernel.org> wrote:
>
> On Thu, Mar 07, 2024 at 07:49:16PM -0800, Alexei Starovoitov wrote:
> > Ok. I think I figured it out.
> > Please try the attached patch.
>
> > PCI address range is managed independently from vmalloc range.
>
> This suggests that the PCI maintainers should be aware of something,
> but I don't know what this means. Can you elaborate on what PCI
> address range management this is, e.g., what functions allocate from
> it? Or how PCI should have been able to avoid this issue?
I believe Chritoph's long term plan for ioremap_page_range()
is to be used for ranges _within_ vmalloc range only.
The vmalloc ranges are allocated by get_vm_area().
In PCI you don't use vmalloc address range.
PCI manages its own PCI_IOBASE, IO_SPACE_LIMIT address range
independently from vmalloc range and they do not overlap.
Hence this proposed patch.
prev parent reply other threads:[~2024-03-08 16:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 17:42 vm_area at addr ffffffffc0800000 is not marked as VM_IOREMAP Miguel Ojeda
2024-03-07 17:54 ` Alexei Starovoitov
2024-03-08 3:49 ` Alexei Starovoitov
2024-03-08 10:48 ` Manivannan Sadhasivam
2024-03-08 11:23 ` Miguel Ojeda
2024-03-08 15:04 ` Christoph Hellwig
2024-03-08 16:33 ` Alexei Starovoitov
2024-03-08 17:02 ` Christoph Hellwig
2024-03-08 17:20 ` Alexei Starovoitov
2024-03-08 17:24 ` Christoph Hellwig
2024-03-08 17:53 ` Alexei Starovoitov
2024-03-08 22:44 ` Alexei Starovoitov
2024-03-09 1:37 ` Alexei Starovoitov
2024-03-09 15:29 ` Christoph Hellwig
2024-03-09 16:33 ` Alexei Starovoitov
2024-03-09 16:36 ` Christoph Hellwig
2024-03-09 16:38 ` Alexei Starovoitov
2024-03-11 11:46 ` Miguel Ojeda
2024-03-08 16:13 ` Bjorn Helgaas
2024-03-08 16:37 ` Alexei Starovoitov [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='CAADnVQJ=_HwPo=Cnemwd095dcsLXKtp=VVBB4bG9_ovfwG8bWw@mail.gmail.com' \
--to=alexei.starovoitov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel@iogearbox.net \
--cc=hch@infradead.org \
--cc=helgaas@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=linux-pci@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).