Was there a way to bind a shared memory object onto a fixed physical memory address?

Was there a way to bind a shared memory object onto a fixed physical memory address?

[kipade]

[-- Attachment #1.1: Type: text/plain, Size: 238 bytes --]

As the topic, I want to specify a fixed physical memory space to a shared memory object, which can use
shm_XXX api to access the memory. Of course I do not want to use mmap api to map /dev/mem device
memory into user program.
Thanks all.

[-- Attachment #1.2: Type: text/html, Size: 492 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Was there a way to bind a shared memory object onto a fixed physical memory address?

[Greg KH]

On Thu, Apr 02, 2020 at 05:38:31PM +0800, kipade wrote:
> As the topic, I want to specify a fixed physical memory space to a shared memory object, which can use
> shm_XXX api to access the memory. Of course I do not want to use mmap api to map /dev/mem device
> memory into user program.

Step back and tell us exactly what problem you have, that you have come
up to this type of solution being necessary?  What do you think you can
solve by doing this?

thanks,

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Was there a way to bind a shared memory object onto a fixed physical memory address?

[kipade]

Im sorry that my there were something wrong about my notebook for a half 
of month.

Here, I want to use system shared memory API to share data across 
processes, but I want it use a specified

range of memory knowned by a slave core such as DSP, etc. If I can do?

thanks.


On 2020/4/2 下午8:19, Greg KH wrote:
> On Thu, Apr 02, 2020 at 05:38:31PM +0800, kipade wrote:
>> As the topic, I want to specify a fixed physical memory space to a shared memory object, which can use
>> shm_XXX api to access the memory. Of course I do not want to use mmap api to map /dev/mem device
>> memory into user program.
> Step back and tell us exactly what problem you have, that you have come
> up to this type of solution being necessary?  What do you think you can
> solve by doing this?
>
> thanks,
>
> greg k-h


_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Was there a way to bind a shared memory object onto a fixed physical memory address?

[Amit Kumar]

[-- Attachment #1.1: Type: text/plain, Size: 1488 bytes --]

On Mon, Apr 20, 2020, 08:33 kipade <kipade@163.com> wrote:

> Im sorry that my there were something wrong about my notebook for a half
> of month.
>
> Here, I want to use system shared memory API to share data across
> processes, but I want it use a specified
> It's simple. As you are mentioning the API, so study that API.
>
I am also trying to learn kernel development, but through reading kernel
documents.
I think a kernel developer should not be fed rather he should eat.
I will suggest you to just take a jump into kernel  documentation
directory, you will find yourself wet.

Pardon me, if I have hurt you.

> range of memory knowned by a slave core such as DSP, etc. If I can do?
>
> thanks.
>
>
> On 2020/4/2 下午8:19, Greg KH wrote:
> > On Thu, Apr 02, 2020 at 05:38:31PM +0800, kipade wrote:
> >> As the topic, I want to specify a fixed physical memory space to a
> shared memory object, which can use
> >> shm_XXX api to access the memory. Of course I do not want to use mmap
> api to map /dev/mem device
> >> memory into user program.
> > Step back and tell us exactly what problem you have, that you have come
> > up to this type of solution being necessary?  What do you think you can
> > solve by doing this?
> >
> > thanks,
> >
> > greg k-h
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>

[-- Attachment #1.2: Type: text/html, Size: 2393 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies