[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] new interface: memory_object_get_proxy
From: |
Samuel Thibault |
Subject: |
Re: [PATCH] new interface: memory_object_get_proxy |
Date: |
Sat, 30 Oct 2021 20:02:39 +0200 |
User-agent: |
NeoMutt/20170609 (1.8.3) |
I forgot to answer this:
Sergey Bugaev, le sam. 30 oct. 2021 15:06:30 +0300, a ecrit:
> > > Should the implementation cap the length to that of the entry
> > > silently, or should it return an error if called with an overly long
> > > len argument?
> > >
> >
> > I don't know, Samuel, what do you think?
>
> Actually now that I think about it, it would probably make sense for
> this to, some day, transparently support proxying multiple regions,
> which is something that the memory object proxies API supports in
> theory (but it's currently unimplemented). So maybe it should return a
> "not yet supported" error for now.
Yes, though we don't have such error, but KERN_INVALID_ARGUMENT would be
fine enough.
Samuel
- Re: gnumach RPC: get info about the calling task, (continued)
- Re: gnumach RPC: get info about the calling task, Sergey Bugaev, 2021/10/17
- Re: gnumach RPC: get info about the calling task, Samuel Thibault, 2021/10/17
- Re: gnumach RPC: get info about the calling task, Joan Lledó, 2021/10/24
- [PATCH] new interface: memory_object_get_proxy, Joan Lledó, 2021/10/24
- Re: [PATCH] new interface: memory_object_get_proxy, Sergey Bugaev, 2021/10/24
- Re: [PATCH] new interface: memory_object_get_proxy, Joan Lledó, 2021/10/30
- Re: [PATCH] new interface: memory_object_get_proxy, Sergey Bugaev, 2021/10/30
- Re: [PATCH] new interface: memory_object_get_proxy, Sergey Bugaev, 2021/10/30
- Re: [PATCH] new interface: memory_object_get_proxy,
Samuel Thibault <=
- Re: [PATCH] new interface: memory_object_get_proxy, Samuel Thibault, 2021/10/30