I've been using the patch posted by Kirill Shutemov
(http://www.mail-archive.com/qemu-devel@nongnu.org/msg10893.html) for
forcing mmap() addresses on 64-bit hosts to be 32-bit clean. I just
discovered a minor problem with the patch: MAP_32BIT is not a valid flag
to mremap() and will cause mremap()
Can QEMU be built from TCC?
Mike
Thayne Harbaugh wrote:
[snip]
> > static inline target_ulong get_sp_from_cpustate(CPUPPCState *state)
> > {
> > return state->gpr[1];
> > }
> >
> > This is no way related to CPU emulation then has nothing to do in cpu.h.
> > Furthermore, there no notion of sigaltstack or even stack pointer in t
On Thursday 27 September 2007 17:27:32 Daniel Jacobowitz wrote:
> On Thu, Sep 27, 2007 at 05:02:46PM +0200, Clemens Kolbitsch wrote:
> > but will kernel mode always use the TLB[0] for address translation (even
> > for addresses at e.g. 0x0800) and user mode TLB[1] (even for e.g.
> > 0xc000abcd)
Hi,
reported yesterday this bug in debian bts
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444160
The same error with self-compiled cvs version today.
Have no clue what's the problem (guest os? amd64?).
Regards
Thomas
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer 07/09/27 16:44:32
Modified files:
linux-user : syscall.c
linux-user/alpha: target_signal.h
linux-user/arm : target_signal.h
linux-user/i386: target_signal.h
linux-u
On Thu, 2007-09-27 at 09:53 -0600, Thayne Harbaugh wrote:
> On Thu, 2007-09-27 at 16:08 +0200, Jocelyn Mayer wrote:
> > On Thu, 2007-09-27 at 13:57 +, Thiemo Seufer wrote:
> > > CVSROOT: /sources/qemu
> > > Module name: qemu
> > > Changes by: Thiemo Seufer 07/09/27 13:57:58
> >
Hi all,
The patch below fully implements supervisor mode, and modify the
the corresponding bits in CP0_Status_rw_bitmask for the CPU which
support this mode.
Bye,
Aurelien
Index: target-mips/exec.h
===
RCS file: /sources/qemu/qemu/
On Thu, 2007-09-27 at 16:08 +0200, Jocelyn Mayer wrote:
> On Thu, 2007-09-27 at 13:57 +, Thiemo Seufer wrote:
> > CVSROOT:/sources/qemu
> > Module name:qemu
> > Changes by: Thiemo Seufer 07/09/27 13:57:58
> >
> > Modified files:
> > linux-user : qemu.h signal.c syscall
On Thu, Sep 27, 2007 at 05:02:46PM +0200, Clemens Kolbitsch wrote:
> but will kernel mode always use the TLB[0] for address translation (even for
> addresses at e.g. 0x0800) and user mode TLB[1] (even for e.g.
> 0xc000abcd)? (or the other way round...)
Which set of TLBs are used depends comp
Jocelyn Mayer wrote:
> On Thu, 2007-09-27 at 13:57 +, Thiemo Seufer wrote:
> > CVSROOT:/sources/qemu
> > Module name:qemu
> > Changes by: Thiemo Seufer 07/09/27 13:57:58
> >
> > Modified files:
> > linux-user : qemu.h signal.c syscall.c
> > target-alpha : cpu.h
Jocelyn Mayer wrote:
> On Thu, 2007-09-27 at 12:48 +, Thiemo Seufer wrote:
> > CVSROOT:/sources/qemu
> > Module name:qemu
> > Changes by: Thiemo Seufer 07/09/27 12:48:12
> >
> > Modified files:
> > target-ppc : translate_init.c
> >
> > Log message:
> > Build fix
On Thursday 27 September 2007 16:01:08 [EMAIL PROTECTED] wrote:
> > does the MEMSUFFIX macro ("kernel" / "user") mean that the memory is
> > access by code running in ring0/ring3 or does this tell about the memory
> > region being access (mem < or > TASK_SIZE / 0xc000)?
>
> The former.
ok :-)
On Thu, 2007-09-27 at 13:57 +, Thiemo Seufer wrote:
> CVSROOT: /sources/qemu
> Module name: qemu
> Changes by: Thiemo Seufer 07/09/27 13:57:58
>
> Modified files:
> linux-user : qemu.h signal.c syscall.c
> target-alpha : cpu.h
> target-arm : cpu.h
>
On Thu, 2007-09-27 at 12:48 +, Thiemo Seufer wrote:
> CVSROOT: /sources/qemu
> Module name: qemu
> Changes by: Thiemo Seufer 07/09/27 12:48:12
>
> Modified files:
> target-ppc : translate_init.c
>
> Log message:
> Build fix for PowerPC hosts, where "PPC" is a pre
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer 07/09/27 13:57:58
Modified files:
linux-user : qemu.h signal.c syscall.c
target-alpha : cpu.h
target-arm : cpu.h
target-i386: cpu.h
target-mips: cpu.h
On Thu, Sep 27, 2007 at 10:39:46AM +0200, Clemens Kolbitsch wrote:
> does the MEMSUFFIX macro ("kernel" / "user") mean that the memory is access
> by
> code running in ring0/ring3 or does this tell about the memory region being
> access (mem < or > TASK_SIZE / 0xc000)?
The former.
> and wh
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer 07/09/27 12:48:12
Modified files:
target-ppc : translate_init.c
Log message:
Build fix for PowerPC hosts, where "PPC" is a predefined macro name.
CVSWeb URLs:
http://cvs.savannah.gnu.org/vi
Ralf Baechle wrote:
Both CONFIG_PCI_NEW and PCI_AUTO were amazingly broken in both concept
and implementation. It is possible to get them to work well for particular
configurations but for the general case nothing else nothing but rewrite
can rescue things.
Hi Ralf,
I found this the hard wa
Blue Swirl wrote:
Someone could port OpenBIOS or LinuxBIOS to MIPS.
Well, just FYI:
I sort-of-ported U-Boot to Qemu (-M mips). Network performance sucks for
some reason (hard enough that tftp-booting a kernel is impossible) and I
didn't have time to investigate this yet. But I guess that p
Alexander Voropay wrote:
<[EMAIL PROTECTED]> wrote:
- QEMU malta emulation is not really complete, to put it mildly
Out of curiosity, what parts did you miss?
Like, for example, the PCI stuff. So I can use the network card.
PCI stuff in the QEMU/Malta works fine, but pseudo-bootrom
does not
Daniel P. Berrange wrote:
> On Wed, Sep 26, 2007 at 06:02:21PM +0200, Laurent Vivier wrote:
>
>> Daniel P. Berrange wrote:
>>
>>> On Wed, Sep 26, 2007 at 05:47:20PM +0200, Laurent Vivier wrote:
>>>
Hi,
I think there is a bug in qemu RTL8139.
RTL8139 uses:
>>>
hi guys!
just a short question:
in softmmu_header.h, for example in function
glue(glue(ld, USUFFIX), MEMSUFFIX)(target_ulong ptr)
which boils down to be included in (e.g.)
op_ldl_kernel_T0_A0
or
op_ldub_user_T0_A0
or
...
does the MEMSUFFIX macro ("kernel" / "user") mean that the memory is acc
23 matches
Mail list logo
