Hi all,
The patch below implements per-cpu decoding on the MIPS target. The
supported instruction set is defined by a set of flags. It assumes that
MIPS2 instructions are always supported. It also removes the check for
CP0C0_AT when setting MIPS_HFLAG_64 as it is now obsolete.
Cheers,
Aurelien
I am running a windows2k guest, which in turn is running coLinux. I
wish to set a breakpoint in the linux instance.
A windows driver loads, and builds the page tables of two independent
virtual address spaces, and backs them with page frames allocated
using the windows driver API. The two addreess
Hi guys!
Short question: I'm having a speech at BlackHat Japan in Oktober about
something I made with qemu. Basically it is a new hardware type (so it is
just an additional file in the hw-subdirectory) --- it's the wireless device
I have been asking questions for a couple of months ago in case s
Hi all,
The patch below moves likely()/unlikely() definitions to exec-all.h
from target-alpha/cpu.h and target-ppc/cpu.h. This way they can be used
on other targets.
Bye,
Aurelien
Index: exec-all.h
===
RCS file: /sources/qemu/qemu/e
On Wed, 19 Sep 2007, Paul Brook wrote:
No. We're doing more than most 32-64 syscall thunks. To a first approximation
the syscall thunks can bindly zero extend all values. In qemu we need to know
whether something is a pointer or a value.
Isn't that was the code in do_syscall() does? or am I lo
Thiemo, in May you added this:
-update_fcr31(); \
+update_fcr31(); \
+if (GET_FP_CAUSE(env->fcr31) & FP_INVALID)\
+FST2 = 0x7fbf;\
+else if (GET_FP_CAUSE(env->fcr31) & FP
On Wednesday 19 September 2007, Stuart Anderson wrote:
> On Wed, 19 Sep 2007, J. Mayer wrote:
> > Then, the changes you've done, changing long arguments (which should be
> > target_long to be correct, you can take a look at the last patch I sent
> > on the list) to pointers, for example in function
On Wed, 2007-09-19 at 15:00 -0400, Stuart Anderson wrote:
> On Wed, 19 Sep 2007, J. Mayer wrote:
>
> > Then, the changes you've done, changing long arguments (which should be
> > target_long to be correct, you can take a look at the last patch I sent
> > on the list) to pointers, for example in fu
On Wed, 19 Sep 2007, J. Mayer wrote:
Then, the changes you've done, changing long arguments (which should be
target_long to be correct, you can take a look at the last patch I sent
on the list) to pointers, for example in function prototypes, are
incorrect.
I just went, and looked at the linux
On Wed, 2007-09-19 at 16:35 +, Hollis Blanchard wrote:
> On Wed, 19 Sep 2007 05:44:04 +, Jocelyn Mayer wrote:
>
> > CVSROOT:/sources/qemu
> > Module name:qemu
> > Changes by: Jocelyn Mayer 07/09/19 05:44:04
> >
> > Modified files:
> > target-ppc : helper.c op.c op_hel
On Wed, 2007-09-19 at 16:35 +0100, Paul Brook wrote:
> > > >> OK, great. Having 64 bits may also help for additional (ie future...)
> > > >> features in PowerPC 64 emulation.
> > > >
> > > > Maybe worth letting the target say whether it needs 32 or 64-bit
> > > > flags.
> > > > The flag lookup is l
On Wed, 19 Sep 2007 05:44:04 +, Jocelyn Mayer wrote:
> CVSROOT: /sources/qemu
> Module name: qemu
> Changes by: Jocelyn Mayer 07/09/19 05:44:04
>
> Modified files:
> target-ppc : helper.c op.c op_helper.c op_helper.h
>translate.c
>
> Log message:
> > >> OK, great. Having 64 bits may also help for additional (ie future...)
> > >> features in PowerPC 64 emulation.
> > >
> > > Maybe worth letting the target say whether it needs 32 or 64-bit
> > > flags.
> > > The flag lookup is likely to be on a hot path.
> > >
>
> I may be wrong, but it seems
On Wednesday 19 September 2007, Stuart Anderson wrote:
> On Wed, 19 Sep 2007, J. Mayer wrote:
> > The idea is great but there seem to be a problem in those patches:
> > you directly cast syscall arguments, which are (or should be)
> > target_ulong to pointers in the host environment. You should to
Ronald wrote:
Nigel Horne schreef:
I don't see this on my systems. It looks like broken kernel headers.
What host (OS version) do you use?
Linux/x86 (F7)
That should have read FC6, sorry.
Thiemo
-Nigel
I think Thiemo also wants to know the kernel version.
[EMAI
On Sep 19, 2007, at 4:39 PM, Jocelyn Mayer wrote:
On Wed, 2007-09-19 at 12:56 +0200, Alexander Graf wrote:
On Sep 19, 2007, at 1:28 AM, Paul Brook wrote:
Ok, I will try to shift the intercepts in an uint_64 flags
variable
in the TB.
OK, great. Having 64 bits may also help for additional
On Wed, 2007-09-19 at 12:56 +0200, Alexander Graf wrote:
> On Sep 19, 2007, at 1:28 AM, Paul Brook wrote:
>
> Ok, I will try to shift the intercepts in an uint_64 flags variable
> in the TB.
> >>
> >> OK, great. Having 64 bits may also help for additional (ie future...)
> >> features in
Nigel Horne schreef:
I don't see this on my systems. It looks like broken kernel headers.
What host (OS version) do you use?
Linux/x86 (F7)
Thiemo
-Nigel
I think Thiemo also wants to know the kernel version.
> I don't see this on my systems. It looks like broken kernel headers.
> What host (OS version) do you use?
Linux/x86 (F7)
>
> Thiemo
>
-Nigel
On Wed, Sep 19, 2007 at 10:28:00PM +1000, Bradley Schatz wrote:
> I have breakpoints failing in the case where a breakpoint is set on a
> virtual address in another virtual address space. The virtual address
> is mapped to nothing in the current virtual address space.
>
> I would like breakpoints
This patch adds the fstatat syscall to linux-user. To depends on the
previous stat64_put_user patch.
Index: qemu/linux-user/syscall.c
===
--- qemu.orig/linux-user/syscall.c 2007-09-19 06:28:34.0 -0600
+++ qemu/linux-user/sysca
This patch puts stat64 functionality into a function rather than using
gotos for all the locations that copy stat64 buffers to user space.
This patch is necessary for following fstatat64 syscall patch.
Index: qemu/linux-user/syscall.c
This patch adds the faccessat syscall to linux-user.
Index: qemu/linux-user/syscall.c
===
--- qemu.orig/linux-user/syscall.c 2007-09-19 06:28:02.0 -0600
+++ qemu/linux-user/syscall.c 2007-09-19 06:28:30.0 -0600
@@ -151,
This patch adds the fchmodat syscall to linux-user.
Index: qemu/linux-user/syscall.c
===
--- qemu.orig/linux-user/syscall.c 2007-09-19 06:27:29.0 -0600
+++ qemu/linux-user/syscall.c 2007-09-19 06:28:02.0 -0600
@@ -151,6
This patch adds the readlinkat syscall to linux-user.
Index: qemu/linux-user/syscall.c
===
--- qemu.orig/linux-user/syscall.c 2007-09-19 06:26:51.0 -0600
+++ qemu/linux-user/syscall.c 2007-09-19 06:27:29.0 -0600
@@ -160
This patch adds the symlinkat syscall to linux-user.
Index: qemu/linux-user/syscall.c
===
--- qemu.orig/linux-user/syscall.c 2007-09-19 06:25:51.0 -0600
+++ qemu/linux-user/syscall.c 2007-09-19 06:26:51.0 -0600
@@ -162,
This patch adds the linkat syscall to linux-user.
Index: qemu/linux-user/syscall.c
===
--- qemu.orig/linux-user/syscall.c 2007-09-19 06:24:47.0 -0600
+++ qemu/linux-user/syscall.c 2007-09-19 06:25:51.0 -0600
@@ -156,6 +
This patch adds the renameat syscall to linux-user.
Index: qemu/linux-user/syscall.c
===
--- qemu.orig/linux-user/syscall.c 2007-09-19 06:23:52.0 -0600
+++ qemu/linux-user/syscall.c 2007-09-19 06:24:47.0 -0600
@@ -159,6
This patch adds the unlinkat syscall to linux-user.
Index: qemu/linux-user/syscall.c
===
--- qemu.orig/linux-user/syscall.c 2007-09-19 06:22:58.0 -0600
+++ qemu/linux-user/syscall.c 2007-09-19 06:23:52.0 -0600
@@ -163,6
This patch adds the fchownat syscall to linux-user.
Index: qemu/linux-user/syscall.c
===
--- qemu.orig/linux-user/syscall.c 2007-09-19 06:21:49.0 -0600
+++ qemu/linux-user/syscall.c 2007-09-19 06:22:58.0 -0600
@@ -151,6
This patch adds the mknodat syscall to linux-user.
Index: qemu/linux-user/syscall.c
===
--- qemu.orig/linux-user/syscall.c 2007-09-19 06:20:59.0 -0600
+++ qemu/linux-user/syscall.c 2007-09-19 06:21:49.0 -0600
@@ -156,6
This patch adds the mkdirat syscall to linux-user.
Index: qemu/linux-user/syscall.c
===
--- qemu.orig/linux-user/syscall.c 2007-09-19 06:19:38.0 -0600
+++ qemu/linux-user/syscall.c 2007-09-19 06:20:59.0 -0600
@@ -155,6
This patch adds the openat syscall to linux-user.
Index: qemu/linux-user/syscall.c
===
--- qemu.orig/linux-user/syscall.c 2007-09-19 06:18:58.0 -0600
+++ qemu/linux-user/syscall.c 2007-09-19 06:19:38.0 -0600
@@ -155,6 +
I have breakpoints failing in the case where a breakpoint is set on a
virtual address in another virtual address space. The virtual address
is mapped to nothing in the current virtual address space.
I would like breakpoints to arbitrarily apply across all virtual
address spaces.
My initial invest
This patch adds the futimesat syscall to linux-user.
Index: qemu/linux-user/syscall.c
===
--- qemu.orig/linux-user/syscall.c 2007-09-19 06:17:45.0 -0600
+++ qemu/linux-user/syscall.c 2007-09-19 06:18:58.0 -0600
@@ -151
Nigel Horne wrote:
> I suddenly remembered I'd forgotten to do a "make clean" after my last
> checkout (oops).
>
> So I did that, and got this compilation error:
>
> ...
> In file included from /home/njh/src/qemu/linux-user/syscall.c:4040:
> /home/njh/src/qemu/linux-user/syscall.c: In function `do
I suddenly remembered I'd forgotten to do a "make clean" after my last checkout
(oops).
So I did that, and got this compilation error:
...
In file included from /home/njh/src/qemu/linux-user/syscall.c:4040:
/home/njh/src/qemu/linux-user/syscall.c: In function `do_syscall':
/usr/include/bits/uni
This patch adds the utimensat syscall to linux-user.
Index: qemu/linux-user/syscall.c
===
--- qemu.orig/linux-user/syscall.c 2007-09-19 06:16:40.0 -0600
+++ qemu/linux-user/syscall.c 2007-09-19 06:17:45.0 -0600
@@ -158,
I have a series of patches to add *at() syscalls to linux-user. The
patches have minor inter-dependencies due to adjacent modifications in
some files.
On Wed, 19 Sep 2007, J. Mayer wrote:
The idea is great but there seem to be a problem in those patches:
you directly cast syscall arguments, which are (or should be)
target_ulong to pointers in the host environment. You should to use the
g2h / h2g macros to get the pointer in the host memory fro
flags64.patch
Description: Binary data
On Sep 19, 2007, at 1:28 AM, Paul Brook wrote:
Ok, I will try to shift the intercepts in an uint_64 flags variable
in the TB.
OK, great. Having 64 bits may also help for additional (ie future...)
features in PowerPC 64 emulation.
Maybe worth letting
On Sep 19, 2007, at 1:28 AM, Paul Brook wrote:
Ok, I will try to shift the intercepts in an uint_64 flags variable
in the TB.
OK, great. Having 64 bits may also help for additional (ie future...)
features in PowerPC 64 emulation.
Maybe worth letting the target say whether it needs 32 or 64-
Nigel Horne wrote:
> The latest CVS snapshot has broken MIPS emulation.
>
> Guest: MIPS debian linux
> Host: Fedora 7/x86
>
> The guest boots as far as
>
> CPU revision is: 00019300
> FPU revision is: 00739300
> Determined physical RAM map:
> memory: 0400 @ (usable)
> Initial ramdisk a
Hi,
On Wed, 19 Sep 2007, Nigel Horne wrote:
> The latest CVS snapshot has broken MIPS emulation.
>
> [...]
>
> Then it hangs.
>
> The last time I tried this guest was a couple of weeks ago, or so, and
> all was fine then.
It would be so good if you could bisect this.
If you have git, clone q
On Wed, 2007-09-19 at 10:07 +0100, Thiemo Seufer wrote:
> J. Mayer wrote:
> > Following my previous message, I did a patch that makes syscalls take
> > target_long/target_ulong argument and return target_long value instead
> > of long/unsigned long.
> > I also included the #ifdef protection for do_
The latest CVS snapshot has broken MIPS emulation.
Guest: MIPS debian linux
Host: Fedora 7/x86
The guest boots as far as
CPU revision is: 00019300
FPU revision is: 00739300
Determined physical RAM map:
memory: 0400 @ (usable)
Initial ramdisk at: 0x802d7000 (2897359 bytes)
Built 1 z
J. Mayer wrote:
> Following my previous message, I did a patch that makes syscalls take
> target_long/target_ulong argument and return target_long value instead
> of long/unsigned long.
> I also included the #ifdef protection for do_socketcall and do_ipc to
> avoid compilation warnings.
> And I als
47 matches
Mail list logo
