linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mary Strodl <mstrodl@freedom.csh.rit.edu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mary Strodl <mstrodl@csh.rit.edu>,
	linux-kernel@vger.kernel.org, urezki@gmail.com,
	hch@infradead.org, linux-mm@kvack.org, lee@kernel.org,
	andi.shyti@kernel.org, linux-i2c@vger.kernel.org,
	s.hauer@pengutronix.de, christian.gmeiner@gmail.com
Subject: Re: [PATCH 1/3] mm: vmalloc: export __vmalloc_node_range
Date: Thu, 18 Jul 2024 08:29:53 -0400	[thread overview]
Message-ID: <ZpkKwfESyr91ekco@freedom.csh.rit.edu> (raw)
In-Reply-To: <20240717195323.d2dbfed9835ba7e2d769921e@linux-foundation.org>

On Wed, Jul 17, 2024 at 07:53:23PM -0700, Andrew Morton wrote:
> Removed by which commit?

Thanks. This was removed in:
88dca4ca5a93 mm: remove the pgprot argument to __vmalloc

It was removed because every driver was passing PAGE_KERNEL

> Why does this driver need a thing which no other driver does?

You can	find more information in the manufacturer's docs:
https://www.congatec.com/fileadmin/user_upload/Documents/Manual/CGOSAPI.pdf

In particular, section 1 (page 11) describes how they intend for
it to work.

Basically, they	provide	an x86 blob in the BIOS	that we	copy
into kernelspace and mark executable. Then, we can call into that
blob to access congatec's special hardware.

Thanks again for reviewing my patches!

If there is a better way to do what I'm trying to do, please let
me know. It's possible I'm missing something obvious.


  reply	other threads:[~2024-07-18 12:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18  1:15 [PATCH 0/3] Add support for Congatec CGEB BIOS interface Mary Strodl
2024-07-18  1:15 ` [PATCH 1/3] mm: vmalloc: export __vmalloc_node_range Mary Strodl
2024-07-18  2:53   ` Andrew Morton
2024-07-18 12:29     ` Mary Strodl [this message]
2024-07-18  3:04   ` Christoph Hellwig
2024-07-18 12:40     ` Mary Strodl
2024-07-18 12:45       ` Matthew Wilcox
2024-07-18 12:49         ` Christoph Hellwig
2024-07-18 12:53           ` Matthew Wilcox
2024-07-18 13:20             ` Mary Strodl
2024-07-18 21:31               ` Andrew Morton
2024-07-18 21:35                 ` Matthew Wilcox
2024-07-18 21:39                   ` Andrew Morton
2024-07-19  6:41                     ` Christian Gmeiner
2024-07-19 11:58                       ` Mary Strodl
2024-07-19 12:42                         ` Matthew Wilcox
2024-07-24  0:00                           ` Andrew Morton
2024-07-24  0:16                             ` Matthew Wilcox
2024-07-24  1:36                               ` Christoph Hellwig
2024-07-19 19:59                         ` Rudolf Marek
2024-07-22 14:54                           ` Mary Strodl
2024-07-18  1:15 ` [PATCH 2/3] x86: Add basic support for the Congatec CGEB BIOS interface Mary Strodl
2024-07-18  3:56   ` kernel test robot
2024-07-18 14:01   ` kernel test robot
2024-07-18  1:15 ` [PATCH 3/3] i2c: Add Congatec CGEB I2C driver Mary Strodl

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=ZpkKwfESyr91ekco@freedom.csh.rit.edu \
    --to=mstrodl@freedom.csh.rit.edu \
    --cc=akpm@linux-foundation.org \
    --cc=andi.shyti@kernel.org \
    --cc=christian.gmeiner@gmail.com \
    --cc=hch@infradead.org \
    --cc=lee@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mstrodl@csh.rit.edu \
    --cc=s.hauer@pengutronix.de \
    --cc=urezki@gmail.com \
    /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