All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Stefan Weil" <sw@weilnetz.de>,
	"Grégory ESTRADE" <gregory.estrade@gmail.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Andrew Baumann" <Andrew.Baumann@microsoft.com>,
	qemu-arm <qemu-arm@nongnu.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [Qemu-arm] [Qemu-devel] [PATCH RFC] bcm2835_dma: add emulation of Raspberry Pi DMA controller
Date: Fri, 04 Mar 2016 09:02:48 +0100	[thread overview]
Message-ID: <1457078568.3574.67.camel@redhat.com> (raw)
In-Reply-To: <CAFEAcA83d79ta+-40_M_mXYs9E=eSQMH9jL7kw-UpPLxK-8Kyw@mail.gmail.com>

  Hi,

> I guess a more general approach to the problem would be to have
> a (hopefully easy) way to say "if this has been going on for too
> long then arrange to defer continued processing of it til later,
> and for now resume the guest".

Doable today, by simply applying some limit and if we hit it schedule a
timer to continue later.

uhci emulation does this, but it's basically no extra work there as usb
emulation is timer based _anyway_.

> That's too big a can of worms for
> this patch, though. (And for something that's only used in TCG
> emulation we care much less about malicious guests than for devices
> that can be used with KVM.)

Agree, given the use case this isn't critical by any means.

cheers,
  Gerd

WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Peter Crosthwaite" <crosthwaite.peter@gmail.com>,
	"Stefan Weil" <sw@weilnetz.de>,
	"Grégory ESTRADE" <gregory.estrade@gmail.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Andrew Baumann" <Andrew.Baumann@microsoft.com>,
	qemu-arm <qemu-arm@nongnu.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC] bcm2835_dma: add emulation of Raspberry Pi DMA controller
Date: Fri, 04 Mar 2016 09:02:48 +0100	[thread overview]
Message-ID: <1457078568.3574.67.camel@redhat.com> (raw)
In-Reply-To: <CAFEAcA83d79ta+-40_M_mXYs9E=eSQMH9jL7kw-UpPLxK-8Kyw@mail.gmail.com>

  Hi,

> I guess a more general approach to the problem would be to have
> a (hopefully easy) way to say "if this has been going on for too
> long then arrange to defer continued processing of it til later,
> and for now resume the guest".

Doable today, by simply applying some limit and if we hit it schedule a
timer to continue later.

uhci emulation does this, but it's basically no extra work there as usb
emulation is timer based _anyway_.

> That's too big a can of worms for
> this patch, though. (And for something that's only used in TCG
> emulation we care much less about malicious guests than for devices
> that can be used with KVM.)

Agree, given the use case this isn't critical by any means.

cheers,
  Gerd

  parent reply	other threads:[~2016-03-04  8:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 23:11 [Qemu-devel] [PATCH RFC] bcm2835_dma: add emulation of Raspberry Pi DMA controller Andrew Baumann
2016-02-29 23:11 ` Andrew Baumann
2016-03-03 14:24 ` [Qemu-arm] " Peter Maydell
2016-03-03 14:24   ` [Qemu-devel] " Peter Maydell
2016-03-03 14:56   ` Grégory ESTRADE
2016-03-03 16:16   ` [Qemu-arm] " Gerd Hoffmann
2016-03-03 16:16     ` Gerd Hoffmann
2016-03-03 16:21     ` Peter Maydell
2016-03-03 17:09       ` Andrew Baumann
2016-03-04  8:02       ` Gerd Hoffmann [this message]
2016-03-04  8:02         ` Gerd Hoffmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1457078568.3574.67.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=Andrew.Baumann@microsoft.com \
    --cc=gregory.estrade@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.