Translate most conditions to TCG conditions and avoid the helper
for most of the common cases.
Signed-off-by: Benjamin Herrenschmidt
---
target-ppc/translate.c | 168 ++---
1 file changed, 132 insertions(+), 36 deletions(-)
diff --git a/target-ppc/tra
Those helpers never load from or store to the TCG tracked environment,
not do they generate synchronous exceptions (they might generate an
asynchronous interrupt but that's not an issue here).
So we can make them all use TCG_CALL_NO_RWG
Signed-off-by: Benjamin Herrenschmidt
---
target-ppc/helpe
They generate exceptions, but they don't update the environment
Signed-off-by: Benjamin Herrenschmidt
---
target-ppc/helper.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target-ppc/helper.h b/target-ppc/helper.h
index b0c1db9..d83086e 100644
--- a/target-ppc/helper.h
We are always generating the "else" case of the condition even when
generating an unconditional branch that will never hit it.
Signed-off-by: Benjamin Herrenschmidt
---
target-ppc/translate.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/target-ppc/translate.
Mostly turn "store" type of helpers into TCG_CALL_NO_WG because
they can take exceptions. Also fixup_thrm doesn't read nor write
the tracked environment.
Signed-off-by: Benjamin Herrenschmidt
---
target-ppc/helper.h | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git
On Fri, Jul 29, 2016 at 03:55:42PM +0200, Igor Mammedov wrote:
> commit f6e98444 (apic: Use apic_id as apic's migration instance_id)
> breaks migration when in kernel irqchip is used for 2.6 and older
> machine types.
>
> It applies compat property only for userspace 'apic' type
> instead of apply
On Sat, Jul 30, 2016 at 09:52:48AM +0200, Jan Kiszka wrote:
[...]
> > +/**
> > + * x86_iommu_iec_notify_all - Notify IEC invalidations
> > + * @iommu: IOMMU device that sends the notification
> > + * @global: whether this is a global invalidation. If true, @index
> > + * and @mask are un
Hi Richard !
So in my discovery of TCG, one thing I noticed is the horrendous amount
of code generated for branches, especially conditional ones.
I have a patch at least to remove a bunch of dead gunk on target-ppc
for non-conditional ones (we still generated the "else" of the
condition even when
On Sat, 2016-07-30 at 16:28 -0400, Programmingkid wrote:
> I was wondering if you could add the 1200x700 resolution to the list
> in https://github.com/ozbenh/QemuMacDrivers/blob/master/QemuVGADriver
> /src/QemuVga.c. This is the perfect resolution for someone
> using QEMU on a 13" MacBook Pro. QE
On Sat, 2016-07-30 at 11:42 -0400, Programmingkid wrote:
>
> I think I can just copy and paste the binary into a file and try
> things that way if necessary.
Nah, just use git am
Cheers,
Ben.
Hello Marek,
On 28.07.2016 15:27, Marek Vasut wrote:
> From: Chris Wulff
>
> Add the Altera timer model.
>
[snip]
> +static void timer_write(void *opaque, hwaddr addr,
> +uint64_t val64, unsigned int size)
> +{
> +AlteraTimer *t = opaque;
> +uint64_t tvalue;
>
I was wondering if you could add the 1200x700 resolution to the list in
https://github.com/ozbenh/QemuMacDrivers/blob/master/QemuVGADriver/src/QemuVga.c.
This is the perfect resolution for someone using QEMU on a 13" MacBook Pro.
QEMU's window fills most of the screen but still allows for easy
> On 30 Jul 2016, at 17:42, Programmingkid wrote:
>
>
> On Jul 27, 2016, at 5:49 PM, Benjamin Herrenschmidt wrote:
>
>> On Wed, 2016-07-27 at 10:33 -0400, Programmingkid wrote:
>>> Could we see the patches you sent to Mark? Right now when I try to
>>> boot QEMU with your patch I see this messa
On Jul 27, 2016, at 5:49 PM, Benjamin Herrenschmidt wrote:
> On Wed, 2016-07-27 at 10:33 -0400, Programmingkid wrote:
>> Could we see the patches you sent to Mark? Right now when I try to
>> boot QEMU with your patch I see this message: qemu-system-ppc:
>> Initialization of device VGA failed: fai
(Intentionally top-posting:)
Hey Eric,
That's really odd. I don't recall changing anything, but I just checked my
(other) e-mail on the nongnu.org's archive and indeed it looks awful. (It looks
fine on both clients I use, though.) Thanks for letting me know, I'll sort this
out.
Cheers,
Felipe
On 2016-07-30 09:41, Jan Kiszka wrote:
> On 2016-07-23 10:12, David Kiarie wrote:
>> Hello all,
>>
>> I, working on AMD IOMMU interrupt remapping would like to ask some
>> questions on Qemu IOAPIC id.
>>
>> I currently have a problem in that Linux AMD IOMMU driver expects at least
>> one IOAPIC on
On Thu, Jul 28, 2016 at 02:22:39PM +0100, Daniel P. Berrange wrote:
> On Thu, Jul 28, 2016 at 12:08:30AM +0900, Namhyung Kim wrote:
> > Add virtio pstore device to allow kernel log files saved on the host.
> > It will save the log files on the directory given by pstore device
> > option.
> >
> >
Hello,
On Thu, Jul 28, 2016 at 02:08:41PM +0100, Daniel P. Berrange wrote:
> On Thu, Jul 28, 2016 at 01:56:07PM +0100, Stefan Hajnoczi wrote:
> > On Thu, Jul 28, 2016 at 02:39:53PM +0900, Namhyung Kim wrote:
> > > On Thu, Jul 28, 2016 at 03:02:54AM +0300, Michael S. Tsirkin wrote:
> > > > On Thu,
On Fri, Jul 29, 2016 at 9:00 PM, Charls D. Chap wrote:
Please use Reply-All when responding to a mailing list thread. This
keeps the mailing list (qemu-devel@nongnu.org) in the CC list so your
replies are sent to the mailing list too. This way the discussion
stays public on the mailing list and
On 07/29/2016 03:16 AM, Andrew Jeffery wrote:
> On Thu, 2016-07-28 at 09:51 +0200, Cédric Le Goater wrote:
>> On 07/28/2016 04:14 AM, Andrew Jeffery wrote:
>>>
>>> On Wed, 2016-07-27 at 18:46 +0200, Cédric Le Goater wrote:
The SCU controler holds the board revision number in its 0x7C
Sorry, only noticed this now in a discussion with David over the AMD IOMMU:
On 2016-07-21 19:53, Michael S. Tsirkin wrote:
> From: Peter Xu
>
> This patch introduces x86 IOMMU IEC (Interrupt Entry Cache)
> invalidation notifier list. When vIOMMU receives IEC invalidate
> request, all the regist
On 2016-07-23 10:12, David Kiarie wrote:
> Hello all,
>
> I, working on AMD IOMMU interrupt remapping would like to ask some
> questions on Qemu IOAPIC id.
>
> I currently have a problem in that Linux AMD IOMMU driver expects at least
> one IOAPIC on the chipset to have ID 0xa0 while Qemu IOAPIC
22 matches
Mail list logo
