Re: [Qemu-devel] [patches] [PATCH v8 10/35] RISC-V: Remove erroneous comment from translate.c

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

Re: [Qemu-devel] [patches] [PATCH v1 1/1] RISC-V: Workaround for critical mstatus.FS MTTCG bug

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

Re: [Qemu-devel] [patches] Re: [PATCH v6 00/26] RISC-V: Fixes and cleanups for QEMU 2.12

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).

Re: [Qemu-devel] [patches] Re: [PATCH v6 00/26] RISC-V: Fixes and cleanups for QEMU 2.12

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

Re: [Qemu-devel] [patches] Re: [PATCH v6 00/26] RISC-V: Fixes and cleanups for QEMU 2.12

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): > > -

Re: [Qemu-devel] [patches] Re: [PATCH v6 00/26] RISC-V: Fixes and cleanups for QEMU 2.12

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

Re: [Qemu-devel] [patches] Re: [PATCH v6 00/26] RISC-V: Fixes and cleanups for QEMU 2.12

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

Re: [Qemu-devel] [patches] Re: [PATCH v6 00/26] RISC-V: Fixes and cleanups for QEMU 2.12

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

Re: [Qemu-devel] [patches] Re: [PATCH v6 00/26] RISC-V: Fixes and cleanups for QEMU 2.12

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

Re: [Qemu-devel] [patches] Re: [PATCH v4 26/26] RISC-V: Fix riscv_isa_string memory size bug

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

Re: [Qemu-devel] [patches] Re: [PATCH v3 00/24] RISC-V Post-merge spec conformance and cleanup

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

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission v8.2

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: >> >

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission v8.2

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:

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission v8.2

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:

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission v8.2

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 >> -

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission v8.2

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 > -

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission 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

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission v8.2

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

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission v8.2

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: >>>

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission v8.2

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

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission

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

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission

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

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission

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

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission

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 > >

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission

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/ >

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission

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

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission

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

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission

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 >

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission

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

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission

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 >

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission

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

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission

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 > >> > >>

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission

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

Re: [Qemu-devel] [patches] Re: [PULL] RISC-V QEMU Port Submission

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: >> >>

Re: [Qemu-devel] Patches

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,

Re: [Qemu-devel] Patches

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

Re: [Qemu-devel] Patches

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

Re: [Qemu-devel] Patches

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

Re: [Qemu-devel] Patches

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

Re: [Qemu-devel] [PATCHES for 1.0] various spice usb-redir integration patches

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

Re: [Qemu-devel] [PATCHES for 1.0] various spice usb-redir integration patches

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

Re: [Qemu-devel] [PATCHES for 1.0] various spice usb-redir integration patches

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

Re: [Qemu-devel] Patches for SMSC LAN911X driver

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

Re: [Qemu-devel] Patches for SMSC LAN911X driver

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,

Re: [Qemu-devel] Patches for OpenBSD support.

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?

Re: [Qemu-devel] Patches in bug tracker also sent to mailing list?

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

Re: [Qemu-devel] Patches in bug tracker also sent to mailing list?

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

Re: [Qemu-devel] Patches?

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.

Re: [Qemu-devel] Patches?

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

Re: [Qemu-devel] Patches?

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

Re: [Qemu-devel] patches for qemu-cvs on NetBSD

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