Signed-off-by: Richard Henderson
---
target-m68k/cpu.h | 1 +
target-m68k/helper.c| 183 +++-
target-m68k/helper.h| 7 ++
target-m68k/translate.c | 142 -
4 files changed, 330 insertions(+), 3 deleti
I believe the first two patches have already been posted.
No changes there, but included here for completeness.
Next is a proposed shift patch, with the changes I believe
I mentioned wanting during review.
Finally, implementations of the bitfield instructions. At least
the register portion depen
Also manage word and byte operands and fix the computation of
overflow in the case of M68000 arithmetic shifts.
Signed-off-by: Laurent Vivier
Signed-off-by: Richard Henderson
---
target-m68k/helper.c| 52
target-m68k/helper.h| 3 -
target-m68k/translate.c | 216 +
From: Laurent Vivier
680x0 movem can load/store words and long words
and can use more addressing modes.
Coldfire can only use long words with (Ax) and (d16,Ax)
addressing modes.
Signed-off-by: Laurent Vivier
Message-Id: <1478121319-31986-3-git-send-email-laur...@vivier.eu>
Signed-off-by: Richar
Report this properly via exception and, importantly, allow
the disassembler the chance to tell us what insn is not handled.
Signed-off-by: Richard Henderson
---
target-m68k/translate.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/target-m68k/translate.c b/target-m6
Signed-off-by: Richard Henderson
---
target-m68k/translate.c | 210
1 file changed, 210 insertions(+)
diff --git a/target-m68k/translate.c b/target-m68k/translate.c
index b538d74..477a511 100644
--- a/target-m68k/translate.c
+++ b/target-m68k/tran
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1617385
Title:
No snapshot
Hi John,
Greetings. Hope you have wonderful weekend.
This is Sanjay Kumar working on a backup and restore solution for KVM.
The QEMU dirty bitmap QMPs support are awesome.
I have below queries in regard to that.
1. How to integrate these QMPs for external backup application.
a) Is the
One more question:
4. How to interpret dirty bitmap file or get list of dirty blocks from the
dirty bitmap in version 2.5?
On Sat, Nov 5, 2016 at 9:29 PM, Sanjay Kumar wrote:
> Hi John,
>
> Greetings. Hope you have wonderful weekend.
>
> This is Sanjay Kumar working on a backup and restore solu
I was looking at your Sparc wiki page and thought it could use a
picture or two. If you could send me a couple, I could add them to
this page: http://wiki.qemu.org/SPARC
On Nov 5, 2016, at 5:53 PM, Peter Maydell wrote:
On 5 November 2016 at 20:45, Peter Maydell
wrote:
Now we have two lists of platforms: one in
http://wiki.qemu.org/Documentation/Platforms
and one in
http://wiki.qemu.org/Documentation
(and the latter doesn't provide any indication that
the for
On 5 November 2016 at 20:45, Peter Maydell wrote:
> Now we have two lists of platforms: one in
> http://wiki.qemu.org/Documentation/Platforms
> and one in
> http://wiki.qemu.org/Documentation
> (and the latter doesn't provide any indication that
> the former exists, but it's where users are most
>
Tested as well 2.7.0, and it now fails on windows start with:
KMODE_EXCEPTION_NOT_HANDLED (viostor.sys)
Notice 2.5.1 still works just fine.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1617114
Tit
On Fri, Nov 4, 2016 at 10:19 PM, Richard Henderson wrote:
> On 11/04/2016 02:50 PM, Artyom Tarasenko wrote:
>>
>> +if (is_exec) { /* XXX has_hypervisor */
>> +if (env->lsu & (IMMU_E)) {
>> +cpu_raise_exception_ra(env, TT_CODE_ACCESS, GETPC());
>> +} else if (cpu_has
On 5 November 2016 at 08:51, Paolo Bonzini wrote:
>
>> > Makes sense. You can also use
>> >
>> > * [{{PagesStartingWith|Documentation/Platforms/}} All platforms emulated by
>> > QEMU]
>> >
>> > instead of listing them manually. Also please add [[Category:User
>> > documentation]]
>> > to the pag
Hi; I had a play on Friday afternoon with Sphinx, which is the
restructured-text documentation processor that the Linux kernel is
just switching to for their documentation. My first impression is
that it would probably be useful for us too (and if the kernel
is using it this also suggests that it's
On Sat, Nov 5, 2016 at 1:17 AM, wrote:
> From: tianqing
>
> Rbd can do readv and writev directly, so wo do not need to transform
> iov to buf or vice versa any more.
>
> Signed-off-by: tianqing
> ---
> block/rbd.c | 124
>
> 1 file
On 11/05/2016 04:07 AM, Cao jin wrote:
CC: Markus Armbruster
CC: Marcel Apfelbaum
CC: Michael S. Tsirkin
Reviewed-by: Markus Armbruster
Signed-off-by: Cao jin
---
hw/pci/msix.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/hw/pci/msix.c b/hw/pci/msix.c
index 0
On 11/05/2016 04:07 AM, Cao jin wrote:
msix_init() reports errors with error_report(), which is wrong when
it's used in realize(). The same issue was fixed for msi_init() in
commit 1108b2f.
For some devices(like e1000e, vmxnet3) who won't fail because of
msix_init's failure, suppress the error
On 11/04/2016 05:01 AM, Cao jin wrote:
On 11/03/2016 07:38 PM, Marcel Apfelbaum wrote:
On 11/03/2016 06:06 AM, Cao jin wrote:
[...]
diff --git a/hw/scsi/megasas.c b/hw/scsi/megasas.c
index 52a4123..fada834 100644
--- a/hw/scsi/megasas.c
+++ b/hw/scsi/megasas.c
@@ -2360,9 +2360,12 @@ st
On 11/03/2016 09:40 PM, Michael S. Tsirkin wrote:
On Thu, Nov 03, 2016 at 01:05:44PM +0200, Marcel Apfelbaum wrote:
On 11/03/2016 06:18 AM, Michael S. Tsirkin wrote:
On Wed, Nov 02, 2016 at 05:16:42PM +0200, Marcel Apfelbaum wrote:
The shpc component is optional while ACPI hotplug is used
for
thanks a lot!I will read the document carefully!
æ�¥è‡ª é…æ—� MX5
原始邮件
�件人：jitendra kumar khasdev
æ—¶é—´ï¼šå‘¨å… 11月5æ—¥ 23:11
收件人：Peter Maydell
抄�：zhun...@gmail.com,qemu-devel
主题：Re: [Qemu-devel] virtIO question
On Nov 5, 2016, at 4:51 AM, Paolo Bonzini wrote:
>
>>> Makes sense. You can also use
>>>
>>> * [{{PagesStartingWith|Documentation/Platforms/}} All platforms emulated by
>>> QEMU]
>>>
>>> instead of listing them manually. Also please add [[Category:User
>>> documentation]]
>>> to the pages.
>
>
> Have you looked at the virtio specification?
No.
> This describes
> the overall structure and communication mechanism, which
> QEMU and Linux each only implement one half of:
> http://docs.oasis-open.org/virtio/virtio/v1.0/virtio-v1.0.html
Thanks Peter. This doc looks me interesting.
---
On 5 November 2016 at 14:46, jitendra kumar khasdev wrote:
> here is what I find difficulty in understanding the code,
>
> 1. Qemu virtio datastructures are not so clear.
> 2. I didn't find any sort high level design with respective qemu for virtIO.
> 3. How qemu virtIO and linux virtIO does share
Hi All,
I am also exploring virtio implementation in qemu, I try to understand
virtio in linux(guest) and qemu, but I am not able to understand I/O stack
between linux to qemu.
here is what I find difficulty in understanding the code,
1. Qemu virtio datastructures are not so clear.
2. I didn't f
who can explain the means of idx in VRingUsed and VRingAvail structure about
virtIO??
thanks!
zhun...@gmail.com
On 5 November 2016 at 00:00, Alistair Francis
wrote:
> The Cadence UART device emulator calculates speed by dividing the
> baud rate by a 'baud rate generator' & 'baud rate divider' value.
> The device specification defines these register values to be
> non-zero and within certain limits. Checks w
>
> Subject: [virtio-dev] Re: [PATCH v12 0/2] virtio-crypto: virtio crypto device
> specification
>
> On Mon, Oct 24, 2016 at 06:51:52AM +, Gonglei (Arei) wrote:
> > Ping
> >
> > And the corresponding source code v9 on QEMU side had been posted:
> >
> > [PATCH v9 00/12] virtio-crypto: int
> > Makes sense. You can also use
> >
> > * [{{PagesStartingWith|Documentation/Platforms/}} All platforms emulated by
> > QEMU]
> >
> > instead of listing them manually. Also please add [[Category:User
> > documentation]]
> > to the pages.
> >
> > Paolo
>
> Thanks. Done.
Good, but don't cre
Signed-off-by: Chao Peng
---
hw/i386/pc.c | 29 -
hw/i386/pc_q35.c | 24 ++--
include/hw/i386/pc.h | 2 ++
3 files changed, 40 insertions(+), 15 deletions(-)
diff --git a/hw/i386/pc.c b/hw/i386/pc.c
index 95d68d5..c5c65ce 100644
--- a/
Signed-off-by: Chao Peng
---
hw/i386/pc.c | 21 -
hw/i386/pc_piix.c| 2 +-
hw/i386/pc_q35.c | 3 ++-
include/hw/i386/pc.h | 3 +++
4 files changed, 26 insertions(+), 3 deletions(-)
diff --git a/hw/i386/pc.c b/hw/i386/pc.c
index c5c65ce..f58c75c 100644
--- a
This patch introduces a light weight machine type which shares the
same codebase with existing q35 machine type but with some features
disabled by default.
Signed-off-by: Chao Peng
---
hw/i386/pc_q35.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/hw/i386/pc_q35.c b/hw/
Signed-off-by: Chao Peng
---
hw/i386/pc.c | 18 ++
hw/i386/pc_q35.c | 12 +++-
include/hw/i386/pc.h | 3 +++
3 files changed, 28 insertions(+), 5 deletions(-)
diff --git a/hw/i386/pc.c b/hw/i386/pc.c
index c011552..95d68d5 100644
--- a/hw/i386/pc.c
+++ b/hw/i
This patchset makes SMBUS/SATA/PIT configurable and introduces a new
machine type q35-lite with these features disabled by default. This is
useful for creating light weight virtual machine without boot time
penalty when these devices are unused.
See https://lists.gnu.org/archive/html/qemu-devel/2
35 matches
Mail list logo
