://lore.kernel.org/qemu-devel/20150706183512.15635.915.st...@gimli.home/
Signed-off-by: Luca Wei
---
hw/intc/arm_gicv3_kvm.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/hw/intc/arm_gicv3_kvm.c b/hw/intc/arm_gicv3_kvm.c
index 72ad916d3d..7e90f8b723 100644
--- a/hw/intc/arm_gicv3_kvm.c
+++ b
From: Luca Bonissi
Date: Thu, 3 Aug 2023 02:15:57 +0200
Subject: [PATCH] Fixed incorrect LLONG alignment for openrisc and cris
OpenRISC (or1k) has long long alignment to 4 bytes, but currently not
defined in abitypes.h. This lead to incorrect packing of /epoll_event/
structure and eventually
r container and/or with cross-compiler):
- cris, m68k, microblaze, nios2, or1k, sh4, x86 (32bit)
See include/exec/user/abitypes.h to update the value.
OK, abitypes.h should be updated with the following patch (discard the
previous patch on syscall_defs.h):
Signed-off-by: Luca Bonissi
---
, POWERDOWN,
and CASA.
Re-posting to add "signed-off-by" line. Removing also unused functions
from qemu-sparc (32bit) building, and consequently removed helper patch
(needed only by unused [removed] functions).
Signed-off-by: Luca Bonissi
---
diff -urp a/linux-user/syscall.c b/linux-user
, adding it just now:
==
The or1k epoll_event structure - unlike other architectures - is packed,
so we need to define it as packed in qemu-user, otherwise it leads to
infinite loop due to missing file descriptor in the returned data:
Signed-off-by: Luca Bonissi
---
diff -up a/linux-user/syscall
the 64bit
final uint64_t parameters, leading to incorrect comparison on the RBTree
(only the first call to mmap on the upper 2GB memory will be successful).
Following the patch to fix the bug (re-submit to add "signed-off-by"):
Signed-off-by: Luca Bonissi
---
diff -up a/accel/tcg/use
On qemu-sparc (user-space), the CASA instruction is not handled for
SPARC32 even if the selected cpu (e.g. LEON3) supports it.
Following the patch that works. I created "fake" ld/st_asi helpers: it
seems all works fine, but I don't know if we should make real ld/st
helpers like for SPARC64 use
The or1k epoll_event structure - unlike other architectures - is packed,
so we need to define it as packed in qemu-user, otherwise it leads to
infinite loop due to missing file descriptor in the returned data:
--- qemu-20230327/linux-user/syscall_defs.h.orig 2023-03-27
15:41:42.0 +0200
On 32bit qemu-user targets, memory allocation failed after about 2GB due
to incorrect signed (instead of the correct unsigned) "last" parameter
in pageflags_find and pageflags_next functions (file accel/tcg/user-exec.c).
The parameter, on 32bit targets, will be signed-extent to the 64bit
final
On 29/03/23 18:22, Laurent Vivier wrote:
Le 28/03/2023 à 14:22, Luca Bonissi a écrit :
On 28/03/23 13:55, Thomas Huth wrote:
On 28/03/2023 13.48, Luca Bonissi wrote:
--- qemu-20230327/linux-user/syscall_defs.h 2023-03-27
15:41:42.0 +0200
+++ qemu-20230327/linux-user
On 28/03/23 13:55, Thomas Huth wrote:
On 28/03/2023 13.48, Luca Bonissi wrote:
--- qemu-20230327/linux-user/syscall_defs.h 2023-03-27
15:41:42.0 +0200
+++ qemu-20230327/linux-user/syscall_defs.h.new 2023-03-27
21:43:25.615115126 +0200
@@ -1450,7 +1450,7 @@ struct target_stat
On qemu-sparc64 (userspace) the struct "target_stat64" is not correctly
padded, so the field st_rdev is not correctly aligned and will report
wrong major/minor (e.g. for /dev/zero it reports 0,0x1050 instead of
1,5).
Here patch to solve the issue (it also fixes incorrect size on some field
tch with Slackware-current
build scripts on x86_64 host: all works fine!
Thanks!
Luca
From guest not because
the OS in VM doesn't have a device PCI manager. I want to know if the
device has a fixed address on KVM VM so to force read and write to that
address in the application on VM.
Best regards
Luca Belluardo
Public bug reported:
>From my testing it seems that QEMU built against musl libc crashes on
pthread_cancel cancel calls - if the binary is also built with musl
libc.
Minimal sample:
#include
#include
#include
void* threadfunc(void* ignored) {
while (1) {
pause();
Public bug reported:
Running qemu-system-aarch64 leads to a high CPU consumption on windows
10.
Tested with qemu: 4.0.0-rc4 & 3.1.0 & 2.11.0
Command: qemu_start_command = [
qemu-system-aarch64,
"-pidfile",
target_path + "/qemu" + str(instance) + ".pid",
"-machine"
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1323001
Title:
Netlink socket support for MIPS*
Status in QEMU:
Fix Released
Bug d
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=480eda2eda7c464e252f17ac87ec61bccc14f285
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1323001
This patches solves the issue for me:
http://patchwork.ozlabs.org/patch/346018/
** Tags added: patch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1323001
Title:
Netlink socket support for MIPS*
Public bug reported:
It seems QEMU does not support Netlink socket support on MIPS*
Trying to compile and run this simple program:
#include
#include
#include
int main()
{
int audit_fd = audit_open ();
printf("fd is %d\n", audit_fd);
printf("errno is %d\n", errno);
** Changed in: qemu (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1256546
Title:
qemu-s390x-static: segmentation fault entering chroot
Status
Is this series of patches applyable to sheepdog-stable-0.6 band qemu 1.5.0 ?
I've seen they use async i/o...
MORITA Kazutaka ha scritto:
>Currently, if a sheepdog server exits, all the connecting VMs need to
>be restarted. This series implements a feature to reconnect the
>server, and enables
Public bug reported:
I find that explicit hostfwd commands do not seem to work with
restrict=yes option, even if the docs clearly state that hostfwd should
override restrict setting.
I am using this config:
-net
user,name=test,net=192.168.100.0/24,host=192.168.100.44,restrict=y,hostfwd=tcp:127.0
On Thu, Jul 21, 2011 at 4:49 PM, Anthony Liguori wrote:
[cut]
> And it's really not that much nicer than the C version. The problem with
> C++ is that even though the type system is much, much nicer, it still
> doesn't have introspection or decorators. These two things would be the
> killer feat
} else {
>> + snprintf(buffer, sizeof(buffer), "%" PRIu64 " TB(s)", size >> 40);
>> + }
>> +
>> + return buffer;
>
> This returns a variable from the stack! Please make the target buffer caller
> defined.
It's static, so it's formally correct. But probably not a good idea :)
Luca
d by default.
> It has been discussed for hardware disk design with 4k sectors, and
> somehow there were plans to map sectors so that the Linux partition
> scheme results in nicely aligned filesystem blocks
Ugh, I hope you're wrong ;-) AFAICS remapping will lead only to
headaches... Li
On 9/17/07, J. Mayer <[EMAIL PROTECTED]> wrote:
> On Mon, 2007-09-17 at 23:14 +0200, Luca wrote:
> > > > since I mentionned "you should have used Git", I'll repeat:
> > > > this commit was not disruptive to any of the Git users, and will
> >
ion CVS. If
> there are better ways to get the code then inform your users how to
> use that.
http://brick.kernel.dk/git/?p=qemu.git;a=summary
It's tracking QEMU CVS; you're right that it's not mentioned anywhere
on the site (AFAICS).
You can also DIY with git-cvsimport; see e.g.
http://chneukirchen.org/blog/archive/2006/04/tracking-the-ruby-cvs-with-git.html
Luca
On 8/31/07, Andreas Färber <[EMAIL PROTECTED]> wrote:
>
> Am 31.08.2007 um 21:45 schrieb Luca Tettamanti:
>
> > Andreas Färber ha scritto:
> >> Am 25.08.2007 um 09:37 schrieb Andreas F=E4rber:
> >>
> >>> One of the recent patches (dynticks) has
taly missed you mail. The timers I've used
are POSIX and are supported on *BSD so I guessed they would work on OSX
too... cleary that's not the case.
Can you grep the headers for timer_create? Maybe the prototypes are in a
different file.
Luca
--
Non sempre quello che viene dopo e` progresso.
Alessandro Manzoni
anilla 2.6.22.3 on that machine.
Try:
cat /sys/devices/system/clocksource/clocksource0/available_clocksource
do you see HPET listed twice?
Luca
thus can be
> >> ignored).
> >> VIRTUAL just becomes more accurate with dyntics, before multiple
> >> timers were batched together.
> >>
> >> > Or maybe your host kernel can't support such a high rate.
> >>
> >> I don't know... a simple printf tells me that the signal handler is
> >> called about 1050 times per second, which sounds about right.
> >
> >...unless strace is attached. ptrace()'ing the process really screw up
> >the timing with dynticks; HPET is also affected but the performance
> >hit is not as severe.
> >
> I didn't figure out how you use both hpet and dyn-tick together.
I don't. Only one timer source is active at any time; the selection is
done at startup with -clock option.
> Hpet has periodic timer while dyn-tick is one shot timer each time.
> Is ther a chance that both are working and that's the source of our
> problems?
No, the various sources are exclusive (though it might be possible to
use HPET in one shot mode).
Luca
On 8/22/07, Luca <[EMAIL PROTECTED]> wrote:
> On 8/22/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> > Luca wrote:
> > >>> This is QEMU, with dynticks and HPET:
> > >>>
> > >&
On 8/22/07, Luca <[EMAIL PROTECTED]> wrote:
> I see a lot of sub ms timer_settime(). Many of them are the result of
> ->expire_time being less than the current qemu_get_clock().
False alarm, this was a bug in the debug code :D
Luca
On 8/22/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Luca wrote:
> >>> This is QEMU, with dynticks and HPET:
> >>>
> >>> % time seconds usecs/call callserrors syscall
> >>> -- --- --- - --
On 8/22/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Luca Tettamanti wrote:
> > Il Wed, Aug 22, 2007 at 08:02:07AM +0300, Avi Kivity ha scritto:
> >
> >> Luca Tettamanti wrote:
> >>
> >>
> >>> Actually I'm having troubles with cycleso
Il Wed, Aug 22, 2007 at 08:02:07AM +0300, Avi Kivity ha scritto:
> Luca Tettamanti wrote:
>
> > Actually I'm having troubles with cyclesoak (probably it's calibration),
> > numbers are not very stable across multiple runs...
> >
>
> I've had good
On 8/21/07, Matthew Kent <[EMAIL PROTECTED]> wrote:
> On Sat, 2007-18-08 at 01:11 +0200, Luca Tettamanti wrote:
> > plain text document attachment (clock-hpet)
> > Linux operates the HPET timer in legacy replacement mode, which means that
> > the periodic interrupt of th
Avi Kivity ha scritto:
> Luca Tettamanti wrote:
>> At 1000Hz:
>>
>> QEMU
>> hpet5.5%
>> dynticks 11.7%
>>
>> KVM
>> hpet3.4%
>> dynticks7.3%
>>
>> No surprises here, you can see the additi
On 8/20/07, malc <[EMAIL PROTECTED]> wrote:
> On Mon, 20 Aug 2007, Luca Tettamanti wrote:
>
> > Il Sun, Aug 19, 2007 at 10:31:26PM +0300, Avi Kivity ha scritto:
> >> Luca wrote:
> >>> On 8/19/07, Luca Tettamanti <[EMAIL PROTECTED]> wrote:
> >
Il Sun, Aug 19, 2007 at 10:31:26PM +0300, Avi Kivity ha scritto:
> Luca wrote:
> > On 8/19/07, Luca Tettamanti <[EMAIL PROTECTED]> wrote:
> >
> >> +static uint64_t qemu_next_deadline(void) {
> >> +uint64_t nearest_delta_us = ULLONG_MAX;
> >>
On 8/19/07, Luca Tettamanti <[EMAIL PROTECTED]> wrote:
> +static uint64_t qemu_next_deadline(void) {
> +uint64_t nearest_delta_us = ULLONG_MAX;
> +uint64_t vmdelta_us;
Hum, I introduced a bug here... those vars should be signed.
On the overhead introduced: how do you measure it?
Luca
se the dyn-tick minimum res will be 1msec. I believe it should
> work ok since this is the case without any dyn-tick.
Actually minimum resolution depends on host HZ setting, but - yes -
essentially you have the same behaviour of the "unix" timer, plus the
overhead of reprogramming the t
the improvement in a linux guest
> when running on a windows host ?
The improvements - beyond the refactoring - are either specific to
Linux (HPET timer) or to UNIX in general (dynticks - POSIX timers are
used).
It may be possible to use one-shot timer on windows too, but I'm not
really familiar with win32 API.
Luca
Allow user to override the list of available alarm timers and their
priority. The format of the options is -clock clk1,clk2,...
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
vl.c | 72 +++
1 file changed, 72 inse
AIL PROTECTED]>
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
configure |5 ++
vl.c | 149 +++---
2 files changed, 148 insertions(+), 6 deletions(-)
Inde
ed in the
same way as the RTC timer.
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
vl.c | 57 -
1 file changed, 56 insertions(+), 1 deletion(-)
Index
sted HPET takes precedence over other timers, but of course this can be
overridden.
Patch 4 introduces "dynticks" timer source; patch is mostly based on the work
Dan Kenigsberg. dynticks is now the default alarm timer.
Luca
--
Make the alarm code modular, removing #ifdef from the generic code and
abstract a common interface for all the timer. The result is functionally
equivalent to the old code.
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
vl.c
AIL PROTECTED]>
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
qemu/configure |5 ++
qemu/vl.c | 149 --
2 files changed, 148 insertions(+), 6 deletions(-)
diff --git a/qemu/configure b/qemu/configure
index 365b7fb..38373db 10075
Make the alarm code modular, removing #ifdef from the generic code and
abstract a common interface for all the timer. The result is functionally
equivalent to the old code.
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
qemu/vl.c
ed in the
same way as the RTC timer.
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
qemu/vl.c | 57 ++-
1 files changed, 56 insertions(+), 1 deletions(-)
diff --git a/qemu/vl.c b/qemu/vl.c
index f0b4896..0373beb 100644
--- a/qemu/vl.c
Hello,
in reply to this mail I will send a serie of 4 patches that cleans up and
expands
the alarm timer handling in QEMU. Patches apply to current kvm-userspace tree,
but I think I can rebase it to QEMU svn if desired.
Patch 1 is mostly a cleanup of the existing code; instead of having multiple
Allow user to override the list of available alarm timers and their
priority. The format of the options is -clock clk1,clk2,...
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
qemu/vl.c | 90 --
1 files changed, 72 insertions(
nearest_delta_us = vmdelta_us;
+}
+
+/* Avoid arming the timer to negative, zero, or too low values */
+/* MIN_TIMER_REARM_US should be optimized */
+#define MIN_TIMER_REARM_US 250
+if (nearest_delta_us <= MIN_TIMER_REARM_US)
+nearest_delta_us = MIN_TIMER_REARM_US;
+
+/* check whether a timer is already running */
+if (timer_gettime(host_timer, &timeout))
+perror("gettime");
+current_us = timeout.it_value.tv_sec * 100 +
timeout.it_value.tv_nsec/1000;
+if (current_us && current_us <= nearest_delta_us)
+return;
+
+timeout.it_interval.tv_sec = 0;
+timeout.it_interval.tv_nsec = 0; /* 0 for one-shot timer */
+timeout.it_value.tv_sec = nearest_delta_us / 100;
+timeout.it_value.tv_nsec = nearest_delta_us % 100 * 1000;
+if (timer_settime(host_timer, 0 /* RELATIVE */, &timeout, NULL))
+perror("settime");
+}
+}
+#endif /* DYNAMIC_TICKS */
+
static int saved_argc;
static char **saved_argv;
@@ -7457,6 +7576,11 @@ int main(int argc, char **argv)
case QEMU_OPTION_cpu_vendor:
cpu_vendor_string = optarg;
break;
+#ifdef DYNAMIC_TICKS
+case QEMU_OPTION_no_dyntick:
+use_dynticks = 0;
+break;
+#endif
}
}
}
Luca
--
Se non puoi convincerli, confondili.
On 8/13/07, Daniel P. Berrange <[EMAIL PROTECTED]> wrote:
> On Mon, Aug 13, 2007 at 11:04:46AM +0300, Avi Kivity wrote:
> > Luca Tettamanti wrote:
> > Something like:
> >
> > - try to use HPET (unless -no-rtc selected)
> > - try to use RTC (unless -no-rtc
ed in the same way as the
RTC timer.
HPET must be explicitly enabled with -use-hpet.
Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]>
---
qemu/vl.c | 62 +-
1 files changed, 60 insertions(+), 2 deletions(-)
diff --git a/qemu/vl.c b/qemu
On 6/5/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
Luca Tettamanti wrote:
> Hello,
> I'm testing the new Fedora7 under KVM. As you may know Fedora has
> migrated to the new libata drivers.
>
> ata_piix is unhappy with the PIIX IDE controller provided by QEmu/KVM:
>
Hello,
I'm testing the new Fedora7 under KVM. As you may know Fedora has
migrated to the new libata drivers.
ata_piix is unhappy with the PIIX IDE controller provided by QEmu/KVM:
libata version 2.20 loaded.
ata_piix :00:01.1: version 2.10ac1
PCI: Setting latency timer of device :00:01.1
ows, and looks weird on
> Windows, not very native.
gtk/cocoa exists.
>
> Or platforms other than Windows and Unix.
name them, macosx has X and cocoa mostly supported by major toolkits.
tk+tile works everywhere and is also looking good.
=)
lu
--
Luca Barbato
Gentoo/linux Gentoo/PP
have to handle windows users or
idiotic managers.
--
Luca Barbato
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
Fabrice Bellard wrote:
> Hi,
>
> Concerning the QEMU GUI, my mind slightly evolved since my last posts on
> the topic: I think that a wxWidgets GUI would be the best as it is
> reasonnably portable and because it uses the native GUIs.
wx is nasty at best.
--
Luca Barbato
Gent
issue or not.
The problem got already reported in the gentoo bugzilla and in the
binutils bugzilla.
As I wrote before the issue is in the linker scripts. isn't a ld
problems (it does the right thing) nor a distribution problem (I'm not
so keen on use a older and probably with more
tem info:
gcc-3.4.4, glibc-2.3.5-r0, 2.6.11-gentoo-r9 binutils-2.16
lu
--
Luca Barbato
Gentoo/linux Developer Gentoo/PPC Operational Leader
http://dev.gentoo.org/~lu_zero
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.
a know amd64 issue.
--
"Uhm... l'ho detto o l'ho solo pensato?"
.::. Ziabice aka Luca Gambetta .::.
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
65 matches
Mail list logo
