On Wed, 25 Apr 2018 16:45:13 PDT (-0700), Michael Clark wrote:
Cc: Sagar Karandikar
Cc: Bastian Koppelmann
Cc: Palmer Dabbelt
Cc: Alistair Francis
Signed-off-by: Michael Clark
On Tue, 27 Mar 2018 12:54:47 PDT (-0700), Michael Clark wrote:
This change is a workaround for a bug where mstatus.FS
is not correctly reporting dirty when MTTCG and SMP are
enabled which results in the floating point register file
not being saved during context switches. This a critical
bug for
On Tue, Mar 27, 2018 at 11:39 AM, Michael Clark wrote:
>
> I will divide the series up into 3 branches, and move through them in
> order of priority, with correctness ahead of tidyness:
>
> 1). riscv-qemu-2.12-critical-fixes
> 2). riscv-qemu-2.13-bug-fixes
> 3).
On Tue, Mar 27, 2018 at 2:42 AM, Peter Maydell
wrote:
> On 26 March 2018 at 19:07, Michael Clark wrote:
> > On Sun, Mar 25, 2018 at 8:03 AM, Peter Maydell >
> > wrote:
> >> Hi. It looks to me like a fair number of these
On Mon, Mar 26, 2018 at 04:45:34PM -0700, Michael Clark wrote:
> I've made a tag for the series including the fixes from my own review
> during the weekend (one logic fix and 2 comment of commit log typos, and a
> patch hunk in the wrong commit):
>
> -
On 26 March 2018 at 19:07, Michael Clark wrote:
> On Sun, Mar 25, 2018 at 8:03 AM, Peter Maydell
> wrote:
>> Hi. It looks to me like a fair number of these patches
>> are already reviewed, so we don't need to wait on the
>> rest being reviewed to get
On Mon, Mar 26, 2018 at 4:14 PM, Michael Clark wrote:
>
>
> On Mon, Mar 26, 2018 at 11:07 AM, Michael Clark wrote:
>
>>
>>
>> On Sun, Mar 25, 2018 at 8:03 AM, Peter Maydell
>> wrote:
>>
>>> On 24 March 2018 at 18:13, Michael Clark
On Mon, Mar 26, 2018 at 11:07 AM, Michael Clark wrote:
>
>
> On Sun, Mar 25, 2018 at 8:03 AM, Peter Maydell
> wrote:
>
>> On 24 March 2018 at 18:13, Michael Clark wrote:
>> > This is a series of bug fixes and code cleanups that we
On Sun, Mar 25, 2018 at 8:03 AM, Peter Maydell
wrote:
> On 24 March 2018 at 18:13, Michael Clark wrote:
> > This is a series of bug fixes and code cleanups that we would
> > like to get in before the QEMU 2.12 release. We are respinning
> > v6 of this
On Tue, Mar 20, 2018 at 1:51 PM, Philippe Mathieu-Daudé
wrote:
> Le mar. 20 mars 2018 12:52, Peter Maydell a
> écrit :
>
>> On 19 March 2018 at 21:18, Michael Clark wrote:
>> > This version uses a constant size memory buffer sized for
On Fri, Mar 16, 2018 at 1:06 PM, wrote:
> Hi,
>
> This series seems to have some coding style problems. See output below for
> more information:
>
> Type: series
> Message-id: 1521229281-73637-1-git-send-email-...@sifive.com
> Subject: [Qemu-devel] [PATCH v3 00/24] RISC-V
On Sat, Mar 10, 2018 at 9:11 AM, Michael Clark wrote:
>
>
> On Sat, Mar 10, 2018 at 5:49 AM, Peter Maydell
> wrote:
>
>> On 9 March 2018 at 14:28, Peter Maydell wrote:
>> > NB: there was a test failure on OpenBSD host:
>> >
On Sat, Mar 10, 2018 at 5:49 AM, Peter Maydell
wrote:
> On 9 March 2018 at 14:28, Peter Maydell wrote:
> > NB: there was a test failure on OpenBSD host:
> >
> > TEST: tests/qom-test... (pid=64016)
> > /riscv32/qom/spike_v1.9.1:
On 9 March 2018 at 14:28, Peter Maydell wrote:
> NB: there was a test failure on OpenBSD host:
>
> TEST: tests/qom-test... (pid=64016)
> /riscv32/qom/spike_v1.9.1: **
> ERROR:/home/qemu/tests/qom-test.c:64:test_properties:
On 9 March 2018 at 15:15, Alex Bennée wrote:
>
> Michael Clark writes:
>
>
>>
>> BTW - I've integrated the following 3 branches into the riscv tree:
>>
>> - https://github.com/riscv/riscv-qemu/tree/softfloat-snan-abort-fix
>> -
Michael Clark writes:
>
> BTW - I've integrated the following 3 branches into the riscv tree:
>
> - https://github.com/riscv/riscv-qemu/tree/softfloat-snan-abort-fix
> - https://github.com/riscv/riscv-qemu/tree/riscv-qemu-upstream-v8.2
> -
On Sat, Mar 10, 2018 at 3:28 AM, Peter Maydell
wrote:
> On 8 March 2018 at 19:53, Michael Clark wrote:
> > I re-iterate Palmer's apology.
> >
> > I shouldn't be polling git.qemu.org/qemu.git and answering emails near
> to
> > 3am in the morning after 4
On 8 March 2018 at 19:53, Michael Clark wrote:
> I re-iterate Palmer's apology.
>
> I shouldn't be polling git.qemu.org/qemu.git and answering emails near to
> 3am in the morning after 4 months of working on trying to get the RISC-V
> port in shape to go upstream.
>
> It appears
On Fri, Mar 9, 2018 at 8:29 AM, Palmer Dabbelt wrote:
> On Thu, 08 Mar 2018 03:41:33 PST (-0800), Michael Clark wrote:
>
>> On Fri, 9 Mar 2018 at 12:18 AM, Michael Clark wrote:
>>
>>> On Fri, 9 Mar 2018 at 12:10 AM, Michael Clark wrote:
>>>
On Thu, 08 Mar 2018 03:41:33 PST (-0800), Michael Clark wrote:
On Fri, 9 Mar 2018 at 12:18 AM, Michael Clark wrote:
On Fri, 9 Mar 2018 at 12:10 AM, Michael Clark wrote:
On Thu, 8 Mar 2018 at 11:02 PM, Peter Maydell
wrote:
On 6
On Tue, Mar 6, 2018 at 8:00 AM, Emilio G. Cota wrote:
> On Sat, Mar 03, 2018 at 02:26:12 +1300, Michael Clark wrote:
> > It was qemu-2.7.50 (late 2016). The benchmarks were generated mid last
> year.
> >
> > I can run the benchmarks again... Has it doubled in speed?
>
> It
On Sat, Mar 03, 2018 at 02:26:12 +1300, Michael Clark wrote:
> It was qemu-2.7.50 (late 2016). The benchmarks were generated mid last year.
>
> I can run the benchmarks again... Has it doubled in speed?
It depends on the benchmarks. Small-ish benchmarks such as rv8-bench
show about a 1.5x
On Thu, Mar 1, 2018 at 9:40 AM, Michael Clark wrote:
>
>
> On Thu, Mar 1, 2018 at 12:53 AM, Peter Maydell
> wrote:
>
>> On 28 February 2018 at 00:09, Michael Clark wrote:
>> > I've just talked to SiFive about this. They have agreed
On Thu, Mar 1, 2018 at 11:26 AM, Emilio G. Cota wrote:
> On Wed, Feb 28, 2018 at 13:09:11 +1300, Michael Clark wrote:
> > BTW somewhat coincidentally, the binary translator I wrote; RV8, which is
> > practicaly twice as fast as QEMU only supports privileged ISA v1.9.1 and
> I
> >
On Wed, Feb 28, 2018 at 13:09:11 +1300, Michael Clark wrote:
> BTW somewhat coincidentally, the binary translator I wrote; RV8, which is
> practicaly twice as fast as QEMU only supports privileged ISA v1.9.1 and I
> personally want to keep binary compatiblity with it.
(snip)
> - https://rv8.io/
>
On Thu, Mar 1, 2018 at 12:53 AM, Peter Maydell
wrote:
> On 28 February 2018 at 00:09, Michael Clark wrote:
> > I've just talked to SiFive about this. They have agreed that we can
> remove
> > the sifive_e300 and sifive_u500 boards from the patch series
On 28 February 2018 at 11:53, Peter Maydell wrote:
> With my 'upstream dev' hat on, I tend to be suspicious of this
> line of argument, because in a lot of cases what tends to happen
> is that the code for some new target or device goes in-tree, and
> then the people who
On 28 February 2018 at 00:09, Michael Clark wrote:
> I've just talked to SiFive about this. They have agreed that we can remove
> the sifive_e300 and sifive_u500 boards from the patch series that we are
> going to submit upstream again later this week or early next week. These
>
On Wed, 28 Feb 2018 13:41:25 +1300
Michael Clark wrote:
> On Wed, Feb 28, 2018 at 5:00 AM, Igor Mammedov wrote:
>
> > On Tue, 27 Feb 2018 14:01:05 +
> > Peter Maydell wrote:
> >
> > > On 27 February 2018 at 00:15, Michael
On Wed, Feb 28, 2018 at 5:00 AM, Igor Mammedov wrote:
> On Tue, 27 Feb 2018 14:01:05 +
> Peter Maydell wrote:
>
> > On 27 February 2018 at 00:15, Michael Clark wrote:
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA1
>
On Wed, Feb 28, 2018 at 6:50 AM, Peter Maydell
wrote:
> On 27 February 2018 at 15:50, Stef O'Rear wrote:
> > On Tue, Feb 27, 2018 at 6:01 AM, Peter Maydell
> wrote:
> >> On 27 February 2018 at 00:15, Michael Clark
On Wed, Feb 28, 2018 at 4:50 AM, Stef O'Rear wrote:
> On Tue, Feb 27, 2018 at 6:01 AM, Peter Maydell
> wrote:
> > On 27 February 2018 at 00:15, Michael Clark wrote:
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA1
> >>
> >>
On 27 February 2018 at 15:50, Stef O'Rear wrote:
> On Tue, Feb 27, 2018 at 6:01 AM, Peter Maydell
> wrote:
>> On 27 February 2018 at 00:15, Michael Clark wrote:
>>> The spike_v1.9
>>> machine has been renamed to spike_v1.9.1 to
On Tue, Feb 27, 2018 at 6:01 AM, Peter Maydell wrote:
> On 27 February 2018 at 00:15, Michael Clark wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> The following changes since commit 0a773d55ac76c5aa89ed9187a3bc5af8c5c2a6d0:
>>
>>
On Wed, Jul 15, 2015 at 12:26:44PM +0100, Peter Maydell wrote:
On 15 July 2015 at 09:52, Stefan Hajnoczi stefa...@redhat.com wrote:
On Tue, Jul 14, 2015 at 10:58:41AM +0100, Peter Maydell wrote:
On 14 July 2015 at 09:12, Peter Crosthwaite
peter.crosthwa...@xilinx.com wrote:
Hi Stefan,
On Tue, Jul 14, 2015 at 10:58:41AM +0100, Peter Maydell wrote:
On 14 July 2015 at 09:12, Peter Crosthwaite
peter.crosthwa...@xilinx.com wrote:
Hi Stefan, Peter,
Is patches down? I don't see any patches for the last 3 days and there
is definitely new things on list:
$ ./patches fetch
On 15 July 2015 at 09:52, Stefan Hajnoczi stefa...@redhat.com wrote:
On Tue, Jul 14, 2015 at 10:58:41AM +0100, Peter Maydell wrote:
On 14 July 2015 at 09:12, Peter Crosthwaite
peter.crosthwa...@xilinx.com wrote:
Hi Stefan, Peter,
Is patches down? I don't see any patches for the last 3
Hi Stefan, Peter,
Is patches down? I don't see any patches for the last 3 days and there
is definitely new things on list:
$ ./patches fetch http://vmsplice.net/~patches/patches.json
Fetched info on 689 patch series
Fetching mboxes...
$ ./patches list | more
Message-id:
On 14 July 2015 at 09:12, Peter Crosthwaite
peter.crosthwa...@xilinx.com wrote:
Hi Stefan, Peter,
Is patches down? I don't see any patches for the last 3 days and there
is definitely new things on list:
$ ./patches fetch http://vmsplice.net/~patches/patches.json
Fetched info on 689 patch
On Tue, Jul 14, 2015 at 01:12:22AM -0700, Peter Crosthwaite wrote:
Hi Stefan, Peter,
Is patches down? I don't see any patches for the last 3 days and there
is definitely new things on list:
$ ./patches fetch http://vmsplice.net/~patches/patches.json
Please switch ~/.patchesrc to this new
To all 'patches' tool users,
The patches database at the official URL is now being updated again:
$ patches fetch http://wiki.qemu.org/patches/patches.json
For the past year or so I published the patches database on my
personal domain. This sometimes caused confusion since the official
QEMU URL
Dear Sir/Madam,
How are you? This is Lisa from WellSucceed Embroidery.
We are professional manufacturer of patches. We can supply you high quality
patches including woven patches, embroidery patches and printed patches. We
can produce both small patches and back patches. At this
Hi,
Here comes a bunch of patches inplementing the virtio input device for
review. One patch for the virtio specification. One patch for the
linux kernel. A small patch series for qemu. Please review.
Note that the qemu patch series has dependencies on unmerged input layer
patches (waiting
On 11/19/2011 03:22 AM, Hans de Goede wrote:
Hi All,
Sorry for sending these in so late, I send most of them in before a long time
ago, but then they got stuck on waiting for the big chardev rewrite. Since it
seems clear now that the big chardev rewrite won't happen before 1.0, I would
like to
On 11/21/11 22:05, Anthony Liguori wrote:
On 11/19/2011 03:22 AM, Hans de Goede wrote:
Hi All,
Sorry for sending these in so late, I send most of them in before a
long time
ago, but then they got stuck on waiting for the big chardev rewrite.
Since it
seems clear now that the big chardev
On 11/19/2011 03:22 AM, Hans de Goede wrote:
Hi All,
Sorry for sending these in so late, I send most of them in before a long time
ago, but then they got stuck on waiting for the big chardev rewrite. Since it
seems clear now that the big chardev rewrite won't happen before 1.0, I would
like to
Hi All,
Sorry for sending these in so late, I send most of them in before a long time
ago, but then they got stuck on waiting for the big chardev rewrite. Since it
seems clear now that the big chardev rewrite won't happen before 1.0, I would
like to get these into 1.0 as is.
Thanks Regards,
Hello,
In the driver for the SMSC LAN9118 device (hw/lan9118.c), I modify the code to
update the PM_CTRL register (switch PM_MODE bits to D0 and set (1b) READY bit )
when writing to the BYTE_TEST register.
Writing to PM_CTRL was not permitted before this modification = raise an
harware error
Hi,
Am 11.11.2011 14:44, schrieb Cachet Bertrand:
Patch is contained in the following commit :
https://bitbucket.org/bca/qemu-linaro/changeset/0aa1f76e5141
I have sent this patch to qemu-linaro but Peter Maydell (pm215 on #qemu
IRC channel) told me to send it here because it is against
On 11 November 2011 13:44, Cachet Bertrand bertrand.cac...@heig-vd.ch wrote:
In the driver for the SMSC LAN9118 device (hw/lan9118.c), I modify the code
to update the PM_CTRL register (switch PM_MODE bits to D0 and set (1b) READY
bit ) when writing to the BYTE_TEST register.
As Andreas says,
On Sun, Dec 19, 2010 at 8:59 PM, Brad b...@comstyle.com wrote:
Here are a few patches for OpenBSD support.
Thanks. Could you resend each patch separately and add Signed-off-by:
Brad Smith b...@comstyle.com line before '---' line?
Here are a few patches for OpenBSD support.
From 0477858c78d7e377bf6db8a498f7745a937c799d Mon Sep 17 00:00:00 2001
From: Brad Smith b...@comstyle.com
Date: Sun, 19 Dec 2010 15:17:42 -0500
Subject: [PATCH 1/3] Add support for OpenBSD to QEMU's tap driver.
---
net/tap-bsd.c |8 ++--
1
Hi,
I've submitted two trivial patches against QEMU in its bug tracker:
https://bugs.launchpad.net/qemu/+bug/568053
https://bugs.launchpad.net/qemu/+bug/568442
Is this sufficient or should I also submit them to the mailing list?
Matt
On Thursday 22 April 2010 09:44:33 Kraai, Matt wrote:
Hi,
I've submitted two trivial patches against QEMU in its bug tracker:
https://bugs.launchpad.net/qemu/+bug/568053
https://bugs.launchpad.net/qemu/+bug/568442
Is this sufficient or should I also submit them to the
On Thu, Apr 22, 2010 at 9:44 AM, Kraai, Matt matt.kr...@amo.abbott.com wrote:
I’ve submitted two trivial patches against QEMU in its bug tracker:
https://bugs.launchpad.net/qemu/+bug/568053
https://bugs.launchpad.net/qemu/+bug/568442
Is this sufficient or should I also submit them to the
Hi,
I usually mail out negative test reults but this time I've just
pulled and merged to my 4 different CRIS, PPC and MicroBlaze trees
from upstream and things Just Worked.
Good work to everybody involved!
Cheers,
Edgar
I've fixed a number of problems with the user mode code.
Where's the best place to send/propose/discuss these?
What's the preferred format?
--
Gary Thomas | Consulting for the
MLB Associates |Embedded
On Monday 17 March 2008 07:19:18 am Gary Thomas wrote:
I've fixed a number of problems with the user mode code.
Where's the best place to send/propose/discuss these?
What's the preferred format?
The best place to send patches is this mailing list. I think they have to be a
unified diff, i.e.
On Mon, Mar 17, 2008 at 07:19:18AM -0600, Gary Thomas wrote:
I've fixed a number of problems with the user mode code.
Where's the best place to send/propose/discuss these?
What's the preferred format?
Hello Gary,
Just send the patches to this list as unified diffs, preferably inlined to the
On Mon, Mar 17, 2008 at 10:42:51AM -0600, C.W. Betts wrote:
The best place to send patches is this mailing list.
I think they have to be a unified diff, i.e. diff -u.
I'd also recommend using the '-p' option, which shows the name of the
function that each change is in.
Cheers,
--
Stuart Brady
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After more than 10 hours the article still didn't show up, so I'm resending
just in case
Some patches are present in pkgsrc that should be sent upstream, so I have
attached the patches and some information about the patches below.
patch-aa: some
Some patches are present in pkgsrc that should be sent upstream, so I have
attached the patches and some information about the patches below.
patch-aa: some machines have machine/bswap.h instead of byteswap.h
patch-ab: qemu (op.c) shouldn't be compiled with the stack-protector turned on,
so this
There are two patches included in the mail
1) qemu-sdl-error.diff - patch to capture output from the sdl compile test, and
output it if there
is an error at reporting time (and delete the file when finished)
2) qemu-sdl-whitespace.diff - patch to fix the indentation for the sdl-config
Can anybody review my patches? I have posted them three day ago but have
no response yet.
signature.asc
Description: Digital signature
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
At http://www.boblycat.org/~malc/code/patches/qemu/ you will find
latest audio, gus/opl3 and retrace patches. Highlights of the release:
==
Audio (15_aqemu)
a. Major overhaul of whole audio subsystem
1. Does no longer depend
Hetz Ben Hamo wrote:
Have you tried to see if the same problem appears with KQEMU installed
on Linux host?
Yes, I can confirm that the same thing happens with kqemu installed on
Linux host with Linux guest.
--
Jason Brittain
___
Qemu-devel mailing list
66 matches
Mail list logo