On Fri, Aug 12, 2016 at 09:21:11PM +0200, Samuel Thibault wrote:
> Richard Braun, on Fri 12 Aug 2016 21:16:02 +0200, wrote:
> > On Fri, Aug 12, 2016 at 07:57:48PM +0200, Samuel Thibault wrote:
> > > It becomes more and more clear that we shouldn't steal functions from
> > > glibc into gnumach, it p
Richard Braun, on Fri 12 Aug 2016 21:16:02 +0200, wrote:
> On Fri, Aug 12, 2016 at 07:57:48PM +0200, Samuel Thibault wrote:
> > It becomes more and more clear that we shouldn't steal functions from
> > glibc into gnumach, it poses cross-building issues from Linux.
> >
> > Could somebody contribute
On Fri, Aug 12, 2016 at 09:16:02PM +0200, Richard Braun wrote:
> Note that it's not that "simple" since we'd like implementations that
> aren't naive, i.e. assembly with rep instructions. In particular, it
> makes a huge difference in virtualized guests compared to C-based ones
> because of vmenter
On Fri, Aug 12, 2016 at 07:57:48PM +0200, Samuel Thibault wrote:
> It becomes more and more clear that we shouldn't steal functions from
> glibc into gnumach, it poses cross-building issues from Linux.
>
> Could somebody contribute, or steal from a BSD the following functions,
> to be included in
On Fri, Aug 12, 2016 at 09:07:48PM +0200, Samuel Thibault wrote:
> > I'm curious: what makes it definitely wrong on a PC ?
>
> A PC has BIOS stuff between A and 10.
Right, misread a 0 again.
--
Richard Braun
Richard Braun, on Fri 12 Aug 2016 21:06:48 +0200, wrote:
> On Fri, Aug 12, 2016 at 07:53:08PM +0200, Samuel Thibault wrote:
> > That's what I'm talking about, and that's the second part of the printfs
> > above, and they are wrong: 1-100 is definitely wrong on a PC,
> > and it includes the
On Fri, Aug 12, 2016 at 07:53:08PM +0200, Samuel Thibault wrote:
> That's what I'm talking about, and that's the second part of the printfs
> above, and they are wrong: 1-100 is definitely wrong on a PC,
> and it includes the debugging symbols.
I'm curious: what makes it definitely wrong o
Samuel Thibault, on Fri 12 Aug 2016 19:53:08 +0200, wrote:
> Yes, but only the heap. The load of segments not containing the heap is
> full:
>
> vm_page_load 1-100 1-100
> vm_page_load 7a00-7ffe 7a00-7ffe
(and only loading the available part of the heap would not p
Richard Braun, on Fri 12 Aug 2016 19:57:10 +0200, wrote:
> On Fri, Aug 12, 2016 at 05:17:26PM +0200, Samuel Thibault wrote:
> > biosmem: heap: 114f000-7a00
> >
> > and objdump shows:
> >
> > LOAD off0x1000 vaddr 0x8100 paddr 0x0100 align 2**12
> > filesz 0x0011470
On Fri, Aug 12, 2016 at 07:57:10PM +0200, Richard Braun wrote:
> On Fri, Aug 12, 2016 at 05:17:26PM +0200, Samuel Thibault wrote:
> > biosmem: heap: 114f000-7a00
> >
> > and objdump shows:
> >
> > LOAD off0x1000 vaddr 0x8100 paddr 0x0100 align 2**12
> > filesz 0x0
Hello,
It becomes more and more clear that we shouldn't steal functions from
glibc into gnumach, it poses cross-building issues from Linux.
Could somebody contribute, or steal from a BSD the following functions,
to be included in gnumach/kern/strings.c?
- memcmp
- memcpy
- memmove
- strchr
- str
On Fri, Aug 12, 2016 at 05:17:26PM +0200, Samuel Thibault wrote:
> biosmem: heap: 114f000-7a00
>
> and objdump shows:
>
> LOAD off0x1000 vaddr 0x8100 paddr 0x0100 align 2**12
> filesz 0x00114700 memsz 0x00114700 flags r-x
> LOAD off0x00116000 vaddr 0x81115
Richard Braun, on Fri 12 Aug 2016 19:50:51 +0200, wrote:
> On Fri, Aug 12, 2016 at 07:08:07PM +0200, Samuel Thibault wrote:
> > More precisely though, adding debugging to vm_page_load:
> >
> > vm_page_load 1-100 1-100
> > vm_page_load 100-7a00 114f000-79c41000
> > vm_page_l
On Fri, Aug 12, 2016 at 07:08:07PM +0200, Samuel Thibault wrote:
> More precisely though, adding debugging to vm_page_load:
>
> vm_page_load 1-100 1-100
> vm_page_load 100-7a00 114f000-79c41000
> vm_page_load 7a00-7ffe 7a00-7ffe
>
> I.e. it properly skips t
Samuel Thibault, on Fri 12 Aug 2016 19:08:07 +0200, wrote:
> What is supposed to exclude everything else? (modules, VGA BIOS, etc.)
I'm tempted to apply the attached patch at least to the Debian package
to brown-tape-fix the issue.
What it does is:
- Make biosmem_load_segment look for the bigges
Hello,
Samuel Thibault, on Fri 12 Aug 2016 17:27:42 +0200, wrote:
> Samuel Thibault, on Fri 12 Aug 2016 17:17:26 +0200, wrote:
> > biosmem: heap: 114f000-7a00
> >
> > and objdump shows:
> >
> > LOAD off0x1000 vaddr 0x8100 paddr 0x0100 align 2**12
> > filesz 0x001
Samuel Thibault, on Fri 12 Aug 2016 17:17:26 +0200, wrote:
> biosmem: heap: 114f000-7a00
>
> and objdump shows:
>
> LOAD off0x1000 vaddr 0x8100 paddr 0x0100 align 2**12
> filesz 0x00114700 memsz 0x00114700 flags r-x
> LOAD off0x00116000 vaddr 0x81115000 pa
Brent W. Baccala, on Thu 11 Aug 2016 15:29:27 -1000, wrote:
> On Wed, Aug 10, 2016 at 4:33 AM, Richard Braun <[1]rbr...@sceen.net> wrote:
>
> On Wed, Aug 10, 2016 at 04:26:35PM +0200, Richard Braun wrote:
> > the boot loader (see MULTIBOOT_FLAGS in boothdr.S), and at
> > some point, la
18 matches
Mail list logo