Public bug reported:
I'm running qemu-system-i386 -cdrom /path/to/windows_xp_cd.iso and it will
yields a BSOD with error code STOP 7E in acpi.sys.
This used to work without problems with qemu 1.2.1 and hence is a regression.
** Affects: qemu
Importance: Undecided
Status: New
--
Y
Public bug reported:
Boot Windows XP with
./qemu-system-i386 -device pci-ohci -device usb-tablet
and then with
./qemu-system-i386 -device pci-ohci -device usb-kbd
and you will notice, that the usb keyboard is not detected. In fact,
Windows XP detects the usb tablet and loads the driver for the ta
Public bug reported:
I'm trying to use the usb tablet and the usb keyboard as follows:
./qemu-system-i386 -device pci-ohci -device usb-tablet -device usb-kbd
or
./qemu-system-i386 -device ich9-usb-ehci1 -device ich9-usb-uhci1 -device
usb-tablet -device ich9-usb-uhci2 -device usb-kbd
While Wind
Same as Bug 1096712 I reported
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1091115
Title:
qemu-1.3.0 crashes when installing windows xp
Status in QEMU:
New
Bug description:
These are the co
Public bug reported:
When using the usb keyboard, I can't type the | character. I'm using
german keyboard layout (de) on the host and inside the guest. As a guest
OS, I use Linux (e.g. a recent KNOPPIX cd). To obtain the | character on
a german keyboard, I need to press AltGr + the < or > key, i.e
Actually, the whole < > | key doesn't work. It's just dead. I can't type
any of those characters.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1101210
Title:
qemu 1.3.0: usb keyboard not fully wor
Any comment? The <>| key is still not working in qemu 1.4.2.
** Summary changed:
- qemu 1.3.0: usb keyboard not fully working
+ qemu 1.4.2: usb keyboard not fully working
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.
This bug is more than 4 years old. Why did I even bother writing it? Is
the problem still there in recent qemu versions?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1096714
Title:
qemu 1.3.0: usb
Due to this bug, I cannot start LXD virtual machines on Arch Linux
anymore.
$ lxc start debian10vm
Error: Failed to run: forklimits limit=memlock:unlimited:unlimited --
/usr/bin/qemu-system-x86_64 -S -name debian10vm -uuid
e265f257-85ca-445f-be5c-0170dca5955d -daemonize -cpu host -nographic -ser
qemu-img convert -p does show a percentage completion (but not avg speed
or compression ratio) so this is at least partially done.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/603872
Title:
[Featu
end=0) at
/home/sven/tmp/qemu/target-i386/op_helper.c:1335
1335env->exception_index = intno;
(gdb) bt
#0 raise_interrupt (intno=1, is_int=0, error_code=0, next_eip_addend=0) at
/home/sven/tmp/qemu/target-i386/op_helper.c:1335
#1 0x08182347 in raise_exception (exception_index=1) at
at
/home/sven/tmp/qemu/target-i386/op_helper.c:1335
1335env->exception_index = intno;
(gdb) bt
#0 raise_interrupt (intno=1, is_int=0, error_code=0, next_eip_addend=0) at
/home/sven/tmp/qemu/target-i386/op_helper.c:1335
#1 0x08182347 in raise_exception (exception_index=1) at
/home/sv
ult.
raise_interrupt (intno=1, is_int=0, error_code=0, next_eip_addend=0) at
/home/sven/tmp/qemu/target-i386/op_helper.c:1335
1335env->exception_index = intno;
(gdb) bt
#0 raise_interrupt (intno=1, is_int=0, error_code=0, next_eip_addend=0) at
/home/sven/tmp/qemu/target-i386/op_helper.c:1
** Attachment added: "nl-be keymap for Qemu (incl. qemu-kvm)"
https://bugs.launchpad.net/qemu/+bug/628082/+attachment/1534466/+files/nl-be
--
nl-be keymap is wrong
https://bugs.launchpad.net/bugs/628082
You received this bug notification because you are a member of qemu-
devel-ml, which is su
Public bug reported:
As mentioned on
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/429965 as well as the
kvm mailinglist
(http://thread.gmane.org/gmane.comp.emulators.kvm.devel/14413), the nl-
be keymap does not work. The number keys above the regular keys (non-
numeric keypad numbers) as wel
revert-e19eb22486f258a421108ac22b8380a4e2f16b97.patch'
> makes NFS root on qemu emulated "arm-integrator-cp" boards work for me
> again.
> After finding:
> http://lists.gnu.org/archive/html/qemu-devel/2009-09/msg01173.html
> through Google and reading through the po
xen specific.
wouldn't it be good to prevent multiple access to the same image by
default and add a switch to overwrite it ?
i am sure other people had the same issue as i had (corrupting images) and
would be great to prevent people in the future messing around with data
loss :-)
Sven
7;t work.
> >
>
> There's still the unmanaged use case to worry about. I think qemu can
> default to advisory locking, and management tools can do their own
> locking and always override qemu.
>
> It's too easy to kill an image by starting up another instance right
now.
>
i agree default should be advisory locking and a switch to disable it ..
would that be hard to implement ?
thanks. Sven
>> qemu's ACPI PCI device doesn't seem to be _that_ normal/known. At least
>> a recent Knoppix lists it as "Bridge: Intel Corp.: Inknown device 7013".
>
> Wrong device id, should be 0x7113.
Hmmm, i looked it up, and i think i know why the author "preferred" 7013
instead of 7113.
7113 is 82371AB/
> i just booted a recent knoppix-cd (4.0.2) and i'm trying to enable DMA,
> but it won't work!
>
> I started qemu with that command:
>
> qemu -m 256 -cdrom knoppix.iso -boot d
>
> But inside knoppix, a "hdparm -d1 /dev/hdc" won't work:
> HDIO_SET_DMA failed: Operation not permitted
Ah ha! DMA
>> So using 7113 would mean, that the PIIX4 stuff gets mixed with PIIX3
>> stuff. I don't know, how odd that might seem to some OS.
>
> It's irrelevant to any OS that i know of.
;-)
>> Beside that, a PIIX3-ACPI-device doesn't seem to exist in the
>> pciid-database.
>
> Huh?
# cat /usr/share/mi
> Win2k and Linux 2.6 (w/o kqemu) seem to work fine.
have you reinstalled Win2k?
Or did you somehow manage, to turn an already installed Win2k from a
"Standard PC" into a "ACPI PC" (as the hardware-manager calls it)?
___
Qemu-devel mailing list
Qemu-
> Just a note: setting DMA through hdparm doesn't work on Linux since
> tens of versions ago, it's been depreceted and you have to trust the
> on-boot autodetection (and it works fine -- unless you didn't compile
> the right driver in). It's the same on real machines.
WHAT!?
i have used it with K
)
Also windows-update's green "progress bar" inside the guest is stopping
for let's say 3 or 5 seconds and not moving continuous.
Is anybody experiencing the same or knows the reason?
Thanks,
Sven
signature.asc
Description: OpenPGP digital signature
_
>> 3) async block I/O (not merged yet)
>> It's not in HEAD yet, isn't it?
>
> The pthread-based async patch is a band-aid. No doubt it helps your
> particular case, but it's not the right approach long term.
>
> IDE only supports one outstanding request, so having a thread that runs
> the synchr
>>> IDE only supports one outstanding request, so having a thread that runs
>>> the synchronous block routines appears reasonable. However, SATA and SCSI
>>> both support multiple outstanding requests. The extension to the existing
>>> patch would be simple--increase the number of threads.
>> ???
> Sounds good, so at least it's on its way :-)
> It's on of those big items left on the TODO, so will be good to see go
> in. Then one should implement an ahci host controller for queued
> command support next...
Or use the scsi emulation :-)
>>> Ah, did not know that queueing
on't understand me wrong.
I appreciate your work.
Greetings
Sven
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
clock();
return get_clock();
---
> return val;
++
This is of course an ugly hack and sure to affect performance, but at
least, it makes XP work for me.
Please let me know your thoughts.
Best regards,
Sven Zenker
--
Dr. med. Sven Zenker
Res
.c
--- main.c.org 2005-08-28 14:40:16.0 -0400
+++ main.c 2005-08-28 15:06:31.0 -0400
@@ -110,9 +110,7 @@
int64_t cpu_get_real_ticks(void)
{
-int64_t val;
-asm volatile ("rdtsc" : "=A" (val));
-retu
). Performance isn't the best, though, although I'm lacking
comparisons.
-Sven
Am Mittwoch, den 19.10.2005, 10:18 +0400 schrieb Brad Campbell:
> Brad Campbell wrote:
> > John R. Hogerhuis wrote:
> >
> >> Anyway everything seems to be fitting your theory about Athlon
> >
there with the cycle counts, but to verify, you could try to
apply my previously posted patch that substituted the built-in mechanism
with realtime clock calls (was for 0.7.1, though, I think).
Best,
Sven
Am Montag, den 07.11.2005, 22:46 + schrieb Michael Smith:
> Alexander Toresson gmail.
Hi,
are there any Gentoo-users out there?
Well, here are 2 ebuilds to use newest qemu-version from CVS:
http://bugs.gentoo.org/show_bug.cgi?id=125668
Greetings
Sven
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org
on't understand me wrong.
I appreciate your work.
Greetings
Sven
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
qemu. I thought that they
would have been integrated along with the DMA-patches already.
I would really see how qemu performs with asynch IO enabled. Are there
any patches out there?
Greetings
Sven
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
> I have seen thoughts about asynchronous IO for qemu. I thought that they
> would have been integrated along with the DMA-patches already.
I'm sorry, i read a mail by Fabrice that async block I/O is not merged yet.
___
Qemu-devel mailing list
Qemu-de
wn device 7013".
BTW: how can i test ACPI with Linux?
At least "cat /proc/acpi/info" works fine and shows:
version: 20050309
Greetings
Sven
signature.asc
Description: OpenPGP digital signature
___
Qemu-devel mailing list
Qemu-de
d
Are there some issues with qemu's DMA support and Linux?
(qemu does have DMA support, doesn't it?)
Greetings
Sven
signature.asc
Description: OpenPGP digital signature
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
Add a context structure for future enhancements. No functional
change intended.
Signed-off-by: Sven Schnelle
---
contrib/plugins/execlog.c | 24 ++--
1 file changed, 14 insertions(+), 10 deletions(-)
diff --git a/contrib/plugins/execlog.c b/contrib/plugins/execlog.c
index
Pass the matches array to parse_vaddr_match(), so future address
matches can reuse that function.
Signed-off-by: Sven Schnelle
---
contrib/plugins/execlog.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/contrib/plugins/execlog.c b/contrib/plugins/execlog.c
index
Add a match similar to the afilter address match, but for data
addresses. When an address is specified with '-dfilter=0x12345'
only load/stores to/from address 0x12345 are printed. All other
instructions are hidden.
Signed-off-by: Sven Schnelle
---
contrib/plugins/exec
Allow to match memory ranges with the address matches. This
allows to give a range of adresses like '-dfilter=0-0x400'
which would only log memory accesses between 0 and 400.
Signed-off-by: Sven Schnelle
---
contrib/plugins/execlog.c | 65 +++
1 fi
log instruction in the address range 0x1000 to 0x2000
and accessing data at address 0x388.
Sven Schnelle (4):
plugins/execlog: add struct execlog_ctx
plugins/execlog: pass matches array to parse_vaddr_match
plugins/execlog: add data address match
plugins/execlog: add address range matching
ning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
startup () at src/parisc/head.S:144
144 rsm PSW_I, %r0 /* disable local irqs */
(gdb)
Signed-off-by: Sven Schnelle
-
appropriate mode when connecting
to qemu/gdbstub.
Sven Schnelle (3):
Revert "target/hppa: Drop attempted gdbstub support for hppa64"
target/hppa: add 64 bit support to gdbstub
target/hppa: mask CR_SAR register writes to 5/6 bit in gdbstub
target/hppa/gdbs
Signed-off-by: Sven Schnelle
---
target/hppa/gdbstub.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/hppa/gdbstub.c b/target/hppa/gdbstub.c
index a5b2c80c07..049b2d6381 100644
--- a/target/hppa/gdbstub.c
+++ b/target/hppa/gdbstub.c
@@ -184,7 +184,7 @@ int
Signed-off-by: Sven Schnelle
---
target/hppa/gdbstub.c | 48 +--
1 file changed, 33 insertions(+), 15 deletions(-)
diff --git a/target/hppa/gdbstub.c b/target/hppa/gdbstub.c
index 48a514384f..a5b2c80c07 100644
--- a/target/hppa/gdbstub.c
+++ b/target/hppa
ion can be enabled by adding
-global lsi53c895a.hpux-spin-workaround=on
to the qemu commandline.
Signed-off-by: Sven Schnelle
---
hw/scsi/lsi53c895a.c | 20 ++--
1 file changed, 18 insertions(+), 2 deletions(-)
diff --git a/hw/scsi/lsi53c895a.c b/hw/scsi/lsi53c895a.c
index
log instruction in the address range 0x1000 to 0x2000
and accessing data at address 0x388.
Changes in v2:
- rebased on top of latest master
Sven Schnelle (3):
plugins/execlog: pass matches array to parse_vaddr_match
plugins/execlog: add data address match
plugins/execlog: add address range
Add a match similar to the afilter address match, but for data
addresses. When an address is specified with '-dfilter=0x12345'
only load/stores to/from address 0x12345 are printed. All other
instructions are hidden.
Signed-off-by: Sven Schnelle
---
contrib/plugins/exec
Allow to match memory ranges with the address matches. This
allows to give a range of adresses like '-dfilter=0-0x400'
which would only log memory accesses between 0 and 400.
Signed-off-by: Sven Schnelle
---
contrib/plugins/execlog.c | 73 ++-
1 fi
Pierrick Bouvier writes:
> Hi Sven, thanks for your series.
>
> Yesterday, series for new API to access registers from plugins was
> merged. As part of it, execlog plugin was extended to support this
> [1].
> This conflict with the changes presented here.
>
> Could you p
Peter Maydell writes:
> On Wed, 28 Feb 2024 at 21:12, Sven Schnelle wrote:
>>
>> HP-UX 10.20 seems to make the lsi53c895a spinning on a memory location
>> under certain circumstances. As the SCSI controller and CPU are not
>> running at the same time this loop wi
Peter Maydell writes:
> On Thu, 29 Feb 2024 at 16:54, Sven Schnelle wrote:
>>
>> Peter Maydell writes:
>>
>> > On Wed, 28 Feb 2024 at 21:12, Sven Schnelle wrote:
>> >>
>> >> HP-UX 10.20 seems to make the lsi53c895a spinning on a memory l
Hi Alex,
Alex Bennée writes:
> Sven Schnelle writes:
>> +static void parse_vaddr_match(GArray **matches, char *token)
>> {
>> -uint64_t v = g_ascii_strtoull(match, NULL, 16);
>> +uint64_t low, high;
>> +gchar *endp;
>>
>> -if (!
SCSI processor are usually very short. This keeps the time
until the loop-exit short.
Suggested-by: Peter Maydell
Signed-off-by: Sven Schnelle
---
hw/scsi/lsi53c895a.c | 33 +
1 file changed, 25 insertions(+), 8 deletions(-)
diff --git a/hw/scsi/lsi53c895a.c b/hw
Hi Alex,
Alex Bennée writes:
> Sven Schnelle writes:
> I think we've lost a patch in the re-posting. patchew hasn't seen it
> either:
>
> https://patchew.org/QEMU/20240229150729.1620410-1-sv...@stackframe.org/
>
>> plugins/execlog: add data address match
BALATON Zoltan writes:
> On Thu, 29 Feb 2024, Sven Schnelle wrote:
>> Some OS's like HP-UX 10.20 are spinn
>
> I guess the above line is left here by accident.
Yes.
>> HP-UX 10.20 seems to make the lsi53c895a spinning on a memory location
>> under certain circu
usually very short. This keeps the time until
the loop is exit short.
Suggested-by: Peter Maydell
Signed-off-by: Sven Schnelle
---
Changes in v2:
- update comment in lsi_execute_script()
- reset waiting state and del timer in lsi_execute_script() to
handle the case where script processing is
BALATON Zoltan writes:
> On Thu, 29 Feb 2024, Sven Schnelle wrote:
>> BALATON Zoltan writes:
>> Yes, i changed it to describe the new method:
>>
>>/*
>> * Some windows drivers make the device spin waiting for a memory location
>> * t
To use range_list_from_string() as a replacement in the execlog
plugin, make it accept single numbers instead of a range. This
might also be useful for the already present debug_ranges filtering.
Signed-off-by: Sven Schnelle
---
util/range.c | 5 +
1 file changed, 5 insertions(+)
diff
In preparation of making the parsing part of qemu_set_dfilter_ranges()
available to other users, convert it to return a GList, so the result
can be used with other functions taking a GList of struct Range.
Signed-off-by: Sven Schnelle
---
util/log.c | 36 ++--
1
log instruction in the address range 0x1000 to 0x2000
and accessing data at address 0x388.
Changes in v3:
- extend plugin api to re-use the existing range parsing infrastructure
- export error report api
Changes in v2:
- rebased on top of latest master
Sven Schnelle (12):
util/log: convert
Use append_new_ranges() instead of manually allocating and
filling the new range member.
Signed-off-by: Sven Schnelle
---
util/range.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/util/range.c b/util/range.c
index 7234ab7a53..db535de9a7 100644
--- a/util/range.c
Add a match similar to the afilter address match, but for data
addresses. When an address is specified with '-dfilter=0x12345'
only load/stores to/from address 0x12345 are printed. All other
instructions are hidden.
Signed-off-by: Sven Schnelle
---
contrib/plugins/exec
Add a small inline function to match an address against
a list of ranges.
Signed-off-by: Sven Schnelle
---
include/qemu/range.h | 12
util/log.c | 10 +-
2 files changed, 13 insertions(+), 9 deletions(-)
diff --git a/include/qemu/range.h b/include/qemu/range.h
Introduce range_list_free(), which takes a GList of ranges
and frees the list and each range.
Signed-off-by: Sven Schnelle
---
include/qemu/range.h | 5 +
util/range.c | 5 +
2 files changed, 10 insertions(+)
diff --git a/include/qemu/range.h b/include/qemu/range.h
index
add qemu_plugin_error_print() which is a wrapper around
error_report_err(). This will be used by
qemu_plugin_parse_filter_ranges() to report parse failures.
Signed-off-by: Sven Schnelle
---
include/qemu/qemu-plugin.h | 12
plugins/api.c| 7 +++
plugins/qemu
Export range_list_from_string(), range_contains() and range_list_free()
to allow plugins to parse filter ranges and match them to avoid
reimplementing this functionality.
Signed-off-by: Sven Schnelle
---
include/qemu/qemu-plugin.h | 41
plugins/api.c
In preparation of making qemu_set_dfilter_ranges() available
to other users, move the code to a new function range_list_from_string()
which takes an additional GList argument.
Signed-off-by: Sven Schnelle
---
util/log.c | 16 +++-
1 file changed, 11 insertions(+), 5 deletions
Makes the code a bit easier to read and maintain.
Signed-off-by: Sven Schnelle
---
util/range.c | 119 ++-
1 file changed, 70 insertions(+), 49 deletions(-)
diff --git a/util/range.c b/util/range.c
index db535de9a7..8c463995e7 100644
--- a/util
Instead of doing its own implementation, use the new range
list API to parse and match address lists.
Signed-off-by: Sven Schnelle
---
contrib/plugins/execlog.c | 27 +--
1 file changed, 9 insertions(+), 18 deletions(-)
diff --git a/contrib/plugins/execlog.c b/contrib
Signed-off-by: Sven Schnelle
---
include/qemu/range.h | 7
util/log.c | 74 --
util/range.c | 76
3 files changed, 83 insertions(+), 74 deletions(-)
diff --git a/include/qemu/range.h b
atch, do you think there's a better way?
Thanks!
Sven
Signed-off-by: Sven Schnelle
---
target/hppa/insns.decode | 99
target/hppa/translate.c | 22 +
2 files changed, 72 insertions(+), 49 deletions(-)
diff --git a/target/hppa/insns.decode b/target/hppa/insns.decode
index f5a3f02fd1..8f17e18cd0
interrupt.
Signed-off-by: Sven Schnelle
---
hw/scsi/lsi53c895a.c | 16
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/hw/scsi/lsi53c895a.c b/hw/scsi/lsi53c895a.c
index 4ff9470381..59b88aff3f 100644
--- a/hw/scsi/lsi53c895a.c
+++ b/hw/scsi/lsi53c895a.c
@@ -57
i haven't spent the time to verify whether it's correct or whether
there are additional changes required. Here it is:
>From 6a807653679fde5e3e09a7f27576c673f335fef6 Mon Sep 17 00:00:00 2001
From: Sven Schnelle
Date: Sat, 3 Feb 2024 19:46:07 +0100
Subject: [PATCH] lsi53c895a: free pe
is called it gets confused because s->current is already set. But i
would need the whole logfile to see why this is going wrong, or even
better AmigaOS (which is not free as you already mentioned)
Sven
Alex Bennée writes:
> Sven Schnelle writes:
>
>> In preparation of making the parsing part of qemu_set_dfilter_ranges()
>> available to other users, convert it to return a GList, so the result
>> can be used with other functions taking a GList of struct Range.
>
>
Peter Maydell writes:
> On Thu, 29 Feb 2024 at 20:44, Sven Schnelle wrote:
>>
>> HP-UX 10.20 seems to make the lsi53c895a spinning on a memory location
>> under certain circumstances. As the SCSI controller and CPU are not
>> running at the same time this loop wi
usually very short. This keeps the time until
the loop is exited short.
Suggested-by: Peter Maydell
Signed-off-by: Sven Schnelle
Reviewed-by: Peter Maydell
---
hw/scsi/lsi53c895a.c | 43 +--
hw/scsi/trace-events | 2 ++
2 files changed, 35 insertions(+), 10
Alex Bennée writes:
> Sven Schnelle writes:
>
>> In preparation of making the parsing part of qemu_set_dfilter_ranges()
>> available to other users, convert it to return a GList, so the result
>> can be used with other functions taking a GList of struct Range.
>
>
Alex Bennée writes:
>> So i wonder
>> whether we should convert all of those functions to GArray? (if
>> possible, i haven't checked)
>
> I think that would depend on access patterns and flexibility. For the
> dfilter there is no particular need for sorting and the principle
> operation is a sequ
10.20 which seems to trigger SCRIPTS
loops.
Fixes: b987718bbb ("hw/scsi/lsi53c895a: Fix reentrancy issues in the LSI
controller (CVE-2023-0330)")
Signed-off-by: Sven Schnelle
---
hw/scsi/lsi53c895a.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/scsi/lsi53c895a.c b/hw/scsi/ls
Thomas Huth writes:
> On 28/01/2024 21.22, Sven Schnelle wrote:
>> When the maximum count of SCRIPTS instructions is reached, the code
>> stops execution and returns, but fails to decrement the reentrancy
>> counter. This effectively renders the SCSI controller unusable
>
erefore set the register to 0x3b40, which means:
Link is up, Autonegotation complete, Full Duplex, 100MBit/s Link
speed.
Also clear the mask because this register is read only.
Signed-off-by: Sven Schnelle
---
hw/net/tulip.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/n
Michael Tokarev writes:
> 20.03.2024 03:32, Richard Henderson :
>
>> Richard Henderson (3):
>>target/hppa: Fix assemble_16 insns for wide mode
>>target/hppa: Fix assemble_11a insns for wide mode
>>target/hppa: Fix assemble_12a insns for
Signed-off-by: Sven Schnelle
---
target/hppa/translate.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/target/hppa/translate.c b/target/hppa/translate.c
index f493e207e1..4d2b96f876 100644
--- a/target/hppa/translate.c
+++ b/target/hppa/translate.c
@@ -1213,6 +1213,9 @@ static void
Wide mode provides two more conditions, add them.
Signed-off-by: Sven Schnelle
---
target/hppa/translate.c | 25 +++--
1 file changed, 23 insertions(+), 2 deletions(-)
diff --git a/target/hppa/translate.c b/target/hppa/translate.c
index 8a87996fc1..f493e207e1 100644
--- a
Signed-off-by: Sven Schnelle
---
target/hppa/translate.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/target/hppa/translate.c b/target/hppa/translate.c
index 4d2b96f876..74a9ea0cd8 100644
--- a/target/hppa/translate.c
+++ b/target/hppa/translate.c
@@ -1122,6 +1122,9 @@ static void
Richard Henderson writes:
> On 3/21/24 08:42, Sven Schnelle wrote:
>> Signed-off-by: Sven Schnelle
>> ---
>> target/hppa/translate.c | 3 +++
>> 1 file changed, 3 insertions(+)
>> diff --git a/target/hppa/translate.c b/target/hppa/translate.c
>> index
Richard Henderson writes:
> On 3/21/24 08:42, Sven Schnelle wrote:
>> Wide mode provides two more conditions, add them.
>> Signed-off-by: Sven Schnelle
>> ---
>> target/hppa/translate.c | 25 +++--
>> 1 file changed, 23 insertions(+), 2 de
move it to cpu.h, so it can also be used in hppa_form_gva_psw()
Signed-off-by: Sven Schnelle
---
target/hppa/cpu.h | 10 --
target/hppa/translate.c | 12 +++-
2 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/target/hppa/cpu.h b/target/hppa/cpu.h
index
64 Bit hppa no longer has a fixed 32/32 bit split between space and
offset. Instead it uses 42 bits for the offset. The lower 10 bits of
the space are always zero, leaving 22 bits actually used. Simply or
the values together to build the gva.
Signed-off-by: Sven Schnelle
---
target/hppa
Hi,
in preparation of getting 64bit HP-UX running in qemu, here are a few fixes
to make HP-UX progress a bit further.
Sven Schnelle (3):
target/hppa: use gva_offset_mask() everywhere
target/hppa: mask offset bits in gva
target/hppa: fix building gva for wide mode
target/hppa/cpu.h
x27;t found how this is switched (guess some diag in the
firmware), but linux + seabios seems to handle that as well,
so lets mask out the additional bits.
Signed-off-by: Sven Schnelle
---
target/hppa/cpu.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/target/hppa/cpu.h b/t
Hi Richard,
Richard Henderson writes:
> In particular Figure 2-14 for "data translation disabled" may be
> instructive. Suppose the cpu does not implement all of the physical
> address lines (true for all extant pa-risc cpus; qemu implements 40
> bits to match pa-8500 iirc). Suppose when repor
Richard Henderson writes:
> On 3/24/24 08:41, Sven Schnelle wrote:
>> 7f09e0: val=000fffb0301f r2=110e0f01 r1=01fff600
>> phys=fffb 4K aid=1 pl1=0, pl2=0 type=1 (DATA RW)
>> 'val' is the value constructed from IOR/ISR,
>
> I
q_b, -1, tmp);
So i think the problem is caused by this optimization. Does this ring a
bell? Debugging this is rather hard, alone the logfile above is 6GB in
size...
Thanks,
Sven
Richard Henderson writes:
> On 3/25/24 09:33, Sven Schnelle wrote:
>> diff --git a/target/hppa/translate.c b/target/hppa/translate.c
>> index 7546a5f5a2..56c68a7cbe 100644
>> --- a/target/hppa/translate.c
>> +++ b/target/hppa/translate.c
>> @@ -3847,7 +3849,7 @@
1 - 100 of 263 matches
Mail list logo
