Hello,
this should address an darwin-user issue that has been creeping in
trunk for sometime.
Thanks,
Pierre.
601-darwin-user-fix.diff
Description: Binary data
If DYNAMIC_TICKS is defined qemu does not attepmt to generate SIGALRM at a
constant rate. Rather, the system timer is set to generate SIGALRM only
when it is needed. DYNAMIC_TICKS reduces the number of SIGALRMs sent to
idle dynamic-ticked guests.
Original patch from Dan Kenigsberg <[EMAIL PROTECTED
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 | 292 +--
Linux operates the HPET timer in legacy replacement mode, which means that
the periodic interrupt of the CMOS RTC is not delivered (qemu won't be able
to use /dev/rtc). Add support for HPET (/dev/hpet) as a replacement for the
RTC; the periodic interrupt is delivered via SIGIO and is handled in the
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(+), 18 deletio
On Thu, Aug 16, 2007 at 01:05:41PM -0400, Ben Taylor wrote:
> Personally, I'm not sure why we wouldn't just write out the command line
> data to a file tied to the primary image file
What about a compatible change to the file format: the last 1024 bytes
are either undefined, or, if a certain mark
Is this on the horizon? Is there any interest in it?
jonathan
--
--
Jonathan Kalbfeld
ThoughtWave Technologies LLC
www.thoughtwave.com
+1 323 620 6682
On Thu, 16 Aug 2007, Blue Swirl wrote:
On 8/14/07, Blue Swirl <[EMAIL PROTECTED]> wrote:
Would the framework need any changes to support other targets? Comments welcome.
Replying to myself: Yes, changes may be needed. Some of the DMA
controllers move the data outside CPU loop, but that does n
CVSROOT:/cvsroot/qemu
Module name:qemu
Changes by: Blue Swirl 07/08/16 19:57:27
Modified files:
hw : sparc32_dma.c
Log message:
Remove old leftovers
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/sparc32_dma.c?cvsroot=qemu&r1=1.7&r2=1.8
CVSROOT:/cvsroot/qemu
Module name:qemu
Changes by: Blue Swirl 07/08/16 19:56:27
Modified files:
. : vl.h
hw : esp.c pcnet.c sparc32_dma.c sun4m.c
Log message:
Use qemu_irq for a reset signal between DMA and ESP/Lance
CVSWeb UR
On 8/16/07, Christian MICHON <[EMAIL PROTECTED]> wrote:
> blame it on gmail. this is the default behaviour.
> it's obviously not intended...
At the risk of drifting further off-topic, I'd just point out that you
can press Ctrl-End in the Gmail message window before you type your
reply.
--Ed
On 8/16/07, Paul Brook <[EMAIL PROTECTED]> wrote:
> Yes, I mean the API. However in practice you'd probably want to try and share
> the implementation as well. In short it's likely to need rewriting before
> it's acceptable upstream.
>
> Paul
>
> P.S. Please don't top-post. Consider this your fin
On Thu, 2007-08-16 at 21:41 +0300, Blue Swirl wrote:
> On 8/14/07, Izik Eidus <[EMAIL PROTECTED]> wrote:
> > anyway you have anyidea why it is working with kvm above 4giga and not
> > with qemu??? can you look at how i did the mapping in qemu?
>
> Kqemu is not compatible with >2G, does it change a
On 8/14/07, Izik Eidus <[EMAIL PROTECTED]> wrote:
> anyway you have anyidea why it is working with kvm above 4giga and not
> with qemu??? can you look at how i did the mapping in qemu?
Kqemu is not compatible with >2G, does it change anything if you run
without kqemu?
Also the assembly versions o
On 8/14/07, Blue Swirl <[EMAIL PROTECTED]> wrote:
> Would the framework need any changes to support other targets? Comments
> welcome.
Replying to myself: Yes, changes may be needed. Some of the DMA
controllers move the data outside CPU loop, but that does not make
much difference.
Background: I
When I read Avi's TODO, I basically thought about getting rid of the
long command lines I had to store in scripts. I wanted to write that
command line once, and then forgetting about it, until I needed to
change it.
Instead of inventing great and wonderfully complicated schemes, the
most sensibl
"Jorge Lucángeli Obes" <[EMAIL PROTECTED]> wrote:
> I've been giving some thought to Anthony's idea:
>
> http://kvm.qumranet.com/kvmwiki/Specs/StoringCommandLineInImage
>
> However, maybe I'm just too much on vacations, but I don't seem to
> come up with a nice way of doing this. Everythin
Am 16.08.2007 um 01:52 schrieb Mark Williamson:
I've missed some of the discussion, but wouldn't tar be an obvious
choice? It
can expand easily out to a directory hierarchy containing config
file and
multiple virtual disk files, there are standard tools that can
manipulate it
and standar
On Thursday 16 August 2007, Paul Brook wrote:
> If you really want to get it merged I suggest modifying kqemu to use the
> kvm interface, augmenting the kvm interface if necessary.
This sounds like the way to go.
On Thu, Aug 16, 2007 at 05:01:42PM +0200, Jernej Simon?i? wrote:
> On Thursday, August 16, 2007, 15:49:14, Paul Brook wrote:
>
> > Mainly because the kernel already has one perfectly good virtualization
> > interface.
>
> Weren't both Xen and lguest recently merged to the (upcoming) 2.6.23
> kern
On Thursday 16 August 2007, H. Peter Anvin wrote:
> Jorge Lucángeli Obes wrote:
> > The '#!' trick works nice with scripts, but I don't see it playing
> > very well with images. ¿Comments? ¿Pointers?
>
> Well, you can make it work with a header (you just have to pad it out to
> a fixed length or us
On Thursday 16 August 2007, [EMAIL PROTECTED] wrote:
> This is a very simple proof-of-concept patch that fakes ICMP well enough
> for ping to work.
Speaking of which... does ping work if qemu runs as root?
As to the patch, it looks like it only works if you're testing whether you
actually can pin
On Thursday, August 16, 2007, 15:49:14, Paul Brook wrote:
> Mainly because the kernel already has one perfectly good virtualization
> interface.
Weren't both Xen and lguest recently merged to the (upcoming) 2.6.23
kernel?
--
< Jernej Simonèiè ><><><><>< http://deepthought.ena.si/ >
If it looks
dragoran wrote:
> Bill C. Riemers wrote:
>> You don't need to compile kqemu into the kernel. When I install
>> dkms-kqemu from freshrpms, I do NOT rebuild my kernel. I am fairly
>> certain with Fedora's new policy for extras, there would not be much
>> of a problem getting it added to Fedora. Fo
> > Mainly because the kernel already has one perfectly good virtualization
> > interface. There's very little motivation to add another incompatible
> > one, especially when the implementation is known to be fundamentally
> > flawed, and probably insecure.
> >
> > If you really want to get it merg
Are you referring to the API when you say interface, or the
functionality itself? If the former that's a reasonable argument, but
the latter is not valid since KVM requires a VT or AMD-V-capable
processor, right? KQEMU does not, and therefore [today] works on a
much larger installed base of hardw
On Thursday 16 August 2007, dragoran wrote:
> Bill C. Riemers wrote:
> > You don't need to compile kqemu into the kernel. When I install
> > dkms-kqemu from freshrpms, I do NOT rebuild my kernel. I am fairly
> > certain with Fedora's new policy for extras, there would not be much
> > of a problem
Bill C. Riemers wrote:
You don't need to compile kqemu into the kernel. When I install
dkms-kqemu from freshrpms, I do NOT rebuild my kernel. I am fairly
certain with Fedora's new policy for extras, there would not be much
of a problem getting it added to Fedora. For that matter, it could
p
You don't need to compile kqemu into the kernel. When I install dkms-kqemu
from freshrpms, I do NOT rebuild my kernel. I am fairly certain with
Fedora's new policy for extras, there would not be much of a problem getting
it added to Fedora. For that matter, it could probably get added into the
n
Luca,
One more comment on your patch: the logic in the following condition
does not fit the comment bellow it.
On Mon, Aug 13, 2007 at 10:37:41PM +0200, Luca Tettamanti wrote:
> +if (use_dynamic_ticks() && dynticks_create_timer()) {
> +/* dynticks disabled or failed to create
Sylvain Petreolle wrote:
>> - Message d'origine
>> De : Avi Kivity <[EMAIL PROTECTED]>
>> À : qemu-devel@nongnu.org
>> Cc : [EMAIL PROTECTED]; Jorge Lucángeli Obes <[EMAIL PROTECTED]>
>> Envoyé le : Jeudi, 16 Août 2007, 7h23mn 16s
>> Objet : Re: [Qemu-devel] Re: [kvm-devel] Making qemu ima
- Message d'origine
De : Avi Kivity <[EMAIL PROTECTED]>
À : qemu-devel@nongnu.org
Cc : [EMAIL PROTECTED]; Jorge Lucángeli Obes <[EMAIL PROTECTED]>
Envoyé le : Jeudi, 16 Août 2007, 7h23mn 16s
Objet : Re: [Qemu-devel] Re: [kvm-devel] Making qemu images executable (and
store command line arg
33 matches
Mail list logo
