On Tue, 22 Mar 2022 17:58:19 +
"Dr. David Alan Gilbert" wrote:
> * Andrew Deason (adea...@sinenomine.net) wrote:
> > On Tue, 22 Mar 2022 16:53:05 +
> > "Dr. David Alan Gilbert" wrote:
> >
> > > * Andrew Deason (adea...@sinenomine.net) wrote:
> > > > On Wed, 16 Mar 2022 10:41:41 +0100
>
* Andrew Deason (adea...@sinenomine.net) wrote:
> On Tue, 22 Mar 2022 16:53:05 +
> "Dr. David Alan Gilbert" wrote:
>
> > * Andrew Deason (adea...@sinenomine.net) wrote:
> > > On Wed, 16 Mar 2022 10:41:41 +0100
> > > David Hildenbrand wrote:
> > >
> > > > On 16.03.22 10:37, Dr. David Alan Gi
On Tue, 22 Mar 2022 16:53:05 +
"Dr. David Alan Gilbert" wrote:
> * Andrew Deason (adea...@sinenomine.net) wrote:
> > On Wed, 16 Mar 2022 10:41:41 +0100
> > David Hildenbrand wrote:
> >
> > > On 16.03.22 10:37, Dr. David Alan Gilbert wrote:
> > > > * Peter Maydell (peter.mayd...@linaro.org)
* Andrew Deason (adea...@sinenomine.net) wrote:
> On Wed, 16 Mar 2022 10:41:41 +0100
> David Hildenbrand wrote:
>
> > On 16.03.22 10:37, Dr. David Alan Gilbert wrote:
> > > * Peter Maydell (peter.mayd...@linaro.org) wrote:
> > >> On Wed, 16 Mar 2022 at 07:53, David Hildenbrand wrote:
> > >>>
> >
On 22.03.22 17:39, Andrew Deason wrote:
> On Wed, 16 Mar 2022 10:41:41 +0100
> David Hildenbrand wrote:
>
>> On 16.03.22 10:37, Dr. David Alan Gilbert wrote:
>>> * Peter Maydell (peter.mayd...@linaro.org) wrote:
On Wed, 16 Mar 2022 at 07:53, David Hildenbrand wrote:
>
> On 16.03.22
On Wed, 16 Mar 2022 10:41:41 +0100
David Hildenbrand wrote:
> On 16.03.22 10:37, Dr. David Alan Gilbert wrote:
> > * Peter Maydell (peter.mayd...@linaro.org) wrote:
> >> On Wed, 16 Mar 2022 at 07:53, David Hildenbrand wrote:
> >>>
> >>> On 16.03.22 05:04, Andrew Deason wrote:
> We have a th
On Wed, 16 Mar 2022 10:41:41 +0100
David Hildenbrand wrote:
> On 16.03.22 10:37, Dr. David Alan Gilbert wrote:
> > * Peter Maydell (peter.mayd...@linaro.org) wrote:
> >> On Wed, 16 Mar 2022 at 07:53, David Hildenbrand wrote:
> >>>
> >>> On 16.03.22 05:04, Andrew Deason wrote:
> We have a th
On 16.03.22 10:37, Dr. David Alan Gilbert wrote:
> * Peter Maydell (peter.mayd...@linaro.org) wrote:
>> On Wed, 16 Mar 2022 at 07:53, David Hildenbrand wrote:
>>>
>>> On 16.03.22 05:04, Andrew Deason wrote:
We have a thin wrapper around madvise, called qemu_madvise, which
provides consis
* Peter Maydell (peter.mayd...@linaro.org) wrote:
> On Wed, 16 Mar 2022 at 07:53, David Hildenbrand wrote:
> >
> > On 16.03.22 05:04, Andrew Deason wrote:
> > > We have a thin wrapper around madvise, called qemu_madvise, which
> > > provides consistent behavior for the !CONFIG_MADVISE case, and wo
On Wed, 16 Mar 2022 at 07:53, David Hildenbrand wrote:
>
> On 16.03.22 05:04, Andrew Deason wrote:
> > We have a thin wrapper around madvise, called qemu_madvise, which
> > provides consistent behavior for the !CONFIG_MADVISE case, and works
> > around some platform-specific quirks (some platforms
On 16.03.22 05:04, Andrew Deason wrote:
> We have a thin wrapper around madvise, called qemu_madvise, which
> provides consistent behavior for the !CONFIG_MADVISE case, and works
> around some platform-specific quirks (some platforms only provide
> posix_madvise, and some don't offer all 'advise' t
On Tue, Mar 15, 2022 at 11:04:05PM -0500, Andrew Deason wrote:
> We have a thin wrapper around madvise, called qemu_madvise, which
> provides consistent behavior for the !CONFIG_MADVISE case, and works
> around some platform-specific quirks (some platforms only provide
> posix_madvise, and some don
12 matches
Mail list logo