Isaku Yamahata writes:
> Fix leak in pci_unregister_secondary_bus().
> call qbus_free().
>
> Signed-off-by: Isaku Yamahata
> ---
> hw/pci.c |1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/hw/pci.c b/hw/pci.c
> index a7ff566..25634ed 100644
> --- a/hw/pci.c
> +++ b/
The LDST macro is used to generate ldc and stc instructions that work with a
specific register. However, the SGR register only supports stc up to SH4A,
which supports both stc and ldc. This patch creates two sub-macros named LD
and ST that handle generating ldc and stc instructions separately, and
This series of patch adds support for the missing ldc & stc privileged
instructions with the sgr register. In order to take the difference
of support between SH4A and SH4 (which does not recognize ldc with sgr),
the LDST macro has been split into two simpler macros.
[PATCH 1/2] target-sh4: Split t
Add support for the following missing priviledged intructions:
For SH4:
- stc sgr, Rn
- stc.l sgr, @-Rn
For SH4A:
- ldc Rm, sgr
- ldc.l @Rm+, sgr
---
target-sh4/translate.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/target-sh4/translate.c b/target-sh4/translate.c
i
Hi,
I couldn't see this in the mainline codebase.
Wondering if something else needs to be done in this patch-set.
Thanks and Regards
gautham.
On Tue, Jun 22, 2010 at 04:48:08PM +0530, Gautham R Shenoy wrote:
> Hi,
>
> This is the v5 of the patch-series to have a generic asynchronous task
> of
On Thu, Jul 08, 2010 at 07:49:35PM +0300, Michael S. Tsirkin wrote:
> > > > - to eliminate assumption of pci_bus_new().
> > > > pci_bus_new() assumes that its pci segment is 0.
> > > > keep pci_bus_new() as a convenience wrapper of
> > > > pci_host_bus_new(segment = 0). Thus we can a
Fix leak in pci_unregister_secondary_bus().
call qbus_free().
Signed-off-by: Isaku Yamahata
---
hw/pci.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/hw/pci.c b/hw/pci.c
index a7ff566..25634ed 100644
--- a/hw/pci.c
+++ b/hw/pci.c
@@ -298,6 +298,7 @@ static void pci_un
Fix leak in pci_unregister_secondary_bus().
call qbus_free().
Signed-off-by: Isaku Yamahata
---
hw/pci.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/hw/pci.c b/hw/pci.c
index a7ff566..25634ed 100644
--- a/hw/pci.c
+++ b/hw/pci.c
@@ -298,6 +298,7 @@ static void pci_un
Ping?
Since this is bug fix patches, I'd like to include them
into the next release.
On Wed, Jun 23, 2010 at 04:15:24PM +0900, Isaku Yamahata wrote:
> Maing changes v4 -> v5:
> - split up/reorder patches for bisectability and testability
> - stype fixes.
>
> patch description:
>
> When pci devic
On 07/08/10 15:08, Cam Macdonell wrote:
> Resent (again): Some lines were over 80 characters and debugging is now off.
>
> Support an inter-vm shared memory device that maps a shared-memory object as a
> PCI device in the guest. This patch also supports interrupts between guest by
> communicatin
Resent (again): Some lines were over 80 characters and debugging is now off.
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to
Anthony Liguori writes:
> On 07/08/2010 12:49 PM, Lluís wrote:
>> Hi there.
>>
>> I'm porting into qemu some code I had for bochs. For this purpose, the first
>> part is a backdoor communication channel, such that code in the guest will be
>> able to directly communicate with qemu in a pre-define
Hi all,
My current understanding of Qemu-kvm is such that whenever Guest VM
establish a passthrough to a pci devices, the following happens:
Setup:
- vt-d setup
- Host mmap the device's BAR via /sysfs.
- Host maintain a 'ptr' to that mmap'ed area.
- Host create a mmio slot for the Guest.
- The mm
On 07/08/2010 12:49 PM, Lluís wrote:
Hi there.
I'm porting into qemu some code I had for bochs. For this purpose, the first
part is a backdoor communication channel, such that code in the guest will be
able to directly communicate with qemu in a pre-defined manner (namely, the
decode of an illeg
Hi there.
I'm porting into qemu some code I had for bochs. For this purpose, the first
part is a backdoor communication channel, such that code in the guest will be
able to directly communicate with qemu in a pre-defined manner (namely, the
decode of an illegal instruction).
Right now, this comes
On Fri, Jul 09, 2010 at 12:43:18AM +0900, Isaku Yamahata wrote:
> On Thu, Jul 08, 2010 at 05:04:32PM +0300, Michael S. Tsirkin wrote:
> > On Wed, Jul 07, 2010 at 11:38:58AM +0900, Isaku Yamahata wrote:
> > > But you claim it's only for root bus, not for secondary bus.
> >
> > It is currently, isn'
On 07/03/2010 09:23 AM, Blue Swirl wrote:
On Fri, Jul 2, 2010 at 9:50 AM, Paolo Bonzini wrote:
The *global* env is still unavailable (i.e. no difference WRT poisoning), by
virtue of being defined in exec.h which is not available unless -DNEED_CPU_H
is defined.
So:
| before
David S. Ahern wrote:
>>> As an alternative, what about enhancing the -usb option to note the
>>> maximum version to enable: e.g., -usb v2[,v3]? -usb alone defaults to
>>> uhci/ohci for compatibility with current design. Then ehci can be
>>> enabled by the user. Enabling v2 means v1 is also enabled
On Thu, Jul 08, 2010 at 05:04:32PM +0300, Michael S. Tsirkin wrote:
> On Wed, Jul 07, 2010 at 11:38:58AM +0900, Isaku Yamahata wrote:
> > But you claim it's only for root bus, not for secondary bus.
>
> It is currently, isn't it?
>
> > Now I realized why you've rejected such patches so far.
> > T
On 07/08/10 08:42, Jan Kiszka wrote:
> David S. Ahern wrote:
>>
>> On 07/08/10 01:49, Jan Kiszka wrote:
>>> David Ahern wrote:
Per the EHCI specification a USB 2.0 host controller is comprised of one
high-speed controller and 0 to N USB 1.1 companion host controllers (UHCI
or OHC
David S. Ahern wrote:
>
> On 07/08/10 01:49, Jan Kiszka wrote:
>> David Ahern wrote:
>>> Per the EHCI specification a USB 2.0 host controller is comprised of one
>>> high-speed controller and 0 to N USB 1.1 companion host controllers (UHCI
>>> or OHCI) for low- and full-speed devices. Port routi
On Wed, Jul 07, 2010 at 11:38:58AM +0900, Isaku Yamahata wrote:
> But you claim it's only for root bus, not for secondary bus.
It is currently, isn't it?
> Now I realized why you've rejected such patches so far.
> Then, you also mean the current pci_register_secondary_bus() is broken.
Sorry abou
On 07/08/10 01:49, Jan Kiszka wrote:
> David Ahern wrote:
>> Per the EHCI specification a USB 2.0 host controller is comprised of one
>> high-speed controller and 0 to N USB 1.1 companion host controllers (UHCI or
>> OHCI) for low- and full-speed devices. Port routing and control logic
>> dete
> - we also want a lossy encoding (Jpeg) for some parts (adaptive choice
> between jpeg and png/zlib based on update frequency is comming soon).
Please note that Tight PNG can already switch from PNG to JPEG like the original
Tight was able to switch from Basic/Indexed to Jpeg (if lossy encoding
a
On Thu, Jul 8, 2010 at 3:19 PM, Daniel P. Berrange wrote:
> On Thu, Jul 08, 2010 at 03:10:31PM +0200, Corentin Chary wrote:
>> On Thu, Jul 8, 2010 at 11:48 AM, Daniel P. Berrange
>> wrote:
>> > On Wed, Jul 07, 2010 at 08:57:56PM +0200, Corentin Chary wrote:
>> >> Introduce a new encoding: VNC_EN
On Thu, Jul 08, 2010 at 04:50:52PM +0530, Prerna Saxena wrote:
> On 07/08/2010 02:50 PM, Stefan Hajnoczi wrote:
> >On Thu, Jul 08, 2010 at 10:58:58AM +0530, Prerna Saxena wrote:
> >>[PATCH] Separate monitor command handler interfaces and tracing internals.
> >>
> >>
> >>Signed-off-by: Prerna Saxena
On Wed, Jul 07, 2010 at 11:04:51AM +0900, Isaku Yamahata wrote:
> On Tue, Jul 06, 2010 at 02:23:27PM +0300, Michael S. Tsirkin wrote:
> > bridge config write should trigger updates
> > on the secondary bus. never on the primary bus.
> >
> > Signed-off-by: Michael S. Tsirkin
> > ---
> >
> > Compi
On Thu, Jul 08, 2010 at 03:10:31PM +0200, Corentin Chary wrote:
> On Thu, Jul 8, 2010 at 11:48 AM, Daniel P. Berrange
> wrote:
> > On Wed, Jul 07, 2010 at 08:57:56PM +0200, Corentin Chary wrote:
> >> Introduce a new encoding: VNC_ENCODING_TIGHT_PNG [1] (-269) with a new
> >> tight filter VNC_TIGH
On Thu, Jul 8, 2010 at 11:48 AM, Daniel P. Berrange wrote:
> On Wed, Jul 07, 2010 at 08:57:56PM +0200, Corentin Chary wrote:
>> Introduce a new encoding: VNC_ENCODING_TIGHT_PNG [1] (-269) with a new
>> tight filter VNC_TIGHT_PNG (0x0A). When the client tells it supports the
>> Tight PNG
>> encodi
On Wed, Jul 07, 2010 at 01:34:22PM +0100, Stefan Hajnoczi wrote:
> The VRING_AVAIL_F_NO_INTERRUPT flag is a hint that interrupts should be
> suppressed. It does not guarantee that interrupts will not be raised.
> Therefore, make sure to clear the interrupt after each virtio-blk read.
> This avoids
On 07/08/2010 02:50 PM, Stefan Hajnoczi wrote:
On Thu, Jul 08, 2010 at 10:58:58AM +0530, Prerna Saxena wrote:
[PATCH] Separate monitor command handler interfaces and tracing internals.
Signed-off-by: Prerna Saxena
---
monitor.c | 23 +++
simpletrace.c | 51 ++
On Wed, Jul 07, 2010 at 08:57:56PM +0200, Corentin Chary wrote:
> Introduce a new encoding: VNC_ENCODING_TIGHT_PNG [1] (-269) with a new
> tight filter VNC_TIGHT_PNG (0x0A). When the client tells it supports the
> Tight PNG
> encoding, the server will use tight, but will always send encoding pixel
On Thu, Jul 08, 2010 at 10:58:58AM +0530, Prerna Saxena wrote:
> [PATCH] Separate monitor command handler interfaces and tracing internals.
>
>
> Signed-off-by: Prerna Saxena
> ---
> monitor.c | 23 +++
> simpletrace.c | 51 +--
On Thu, Jul 8, 2010 at 9:28 AM, Stefan Hajnoczi
wrote:
> On Thu, Jul 08, 2010 at 12:12:10PM +0530, Prerna Saxena wrote:
>> Hi Stefan,
>> On 07/07/2010 01:44 AM, Stefan Hajnoczi wrote:
>> >Signed-off-by: Stefan Hajnoczi
>> >---
>> >This applies to the tracing branch at:
>> >
>> > http://repo.or.c
On Thu, Jul 08, 2010 at 12:12:10PM +0530, Prerna Saxena wrote:
> Hi Stefan,
> On 07/07/2010 01:44 AM, Stefan Hajnoczi wrote:
> >Signed-off-by: Stefan Hajnoczi
> >---
> >This applies to the tracing branch at:
> >
> > http://repo.or.cz/w/qemu/stefanha.git/shortlog/refs/heads/tracing-dev
> >
> > si
On Wed, Jul 07, 2010 at 01:34:22PM +0100, Stefan Hajnoczi wrote:
> The VRING_AVAIL_F_NO_INTERRUPT flag is a hint that interrupts should be
> suppressed. It does not guarantee that interrupts will not be raised.
> Therefore, make sure to clear the interrupt after each virtio-blk read.
> This avoids
36 matches
Mail list logo
