Displaying 20 results from an estimated 6000 matches similar to: "[PATCH] MAINTAINERS: separate section for s390 virtio drivers"
2015 Jul 07
1
[PATCH] MAINTAINERS: separate section for s390 virtio drivers
On Wed, 1 Jul 2015 17:17:41 +0200
Paolo Bonzini <pbonzini at redhat.com> wrote:
>
>
> On 01/07/2015 17:15, Cornelia Huck wrote:
> > The s390-specific virtio drivers have probably more to do with virtio
> > than with kvm today; let's move them out into a separate section to
> > reflect this and to be able to add relevant mailing lists.
> >
> >
2015 Jul 07
1
[PATCH] MAINTAINERS: separate section for s390 virtio drivers
On Wed, 1 Jul 2015 17:17:41 +0200
Paolo Bonzini <pbonzini at redhat.com> wrote:
>
>
> On 01/07/2015 17:15, Cornelia Huck wrote:
> > The s390-specific virtio drivers have probably more to do with virtio
> > than with kvm today; let's move them out into a separate section to
> > reflect this and to be able to add relevant mailing lists.
> >
> >
2015 Jul 01
0
[PATCH] MAINTAINERS: separate section for s390 virtio drivers
On 01/07/2015 17:15, Cornelia Huck wrote:
> The s390-specific virtio drivers have probably more to do with virtio
> than with kvm today; let's move them out into a separate section to
> reflect this and to be able to add relevant mailing lists.
>
> CC: Christian Borntraeger <borntraeger at de.ibm.com>
> Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com>
2016 Jul 07
4
[PATCH 0/2] virtio/s390 patches for 4.8
Michael,
here are two virtio/s390 patches for 4.8.
First, Jing Liu noticed that she could trigger panics while playing
around with hvc0 as preferred console but no virtio console: This
can be fixed by not discarding our early_put_chars after init (as
the minimal fix).
This made us wonder why we still have that code around when no current
host code supports the old transport: We have no idea
2016 Jul 07
4
[PATCH 0/2] virtio/s390 patches for 4.8
Michael,
here are two virtio/s390 patches for 4.8.
First, Jing Liu noticed that she could trigger panics while playing
around with hvc0 as preferred console but no virtio console: This
can be fixed by not discarding our early_put_chars after init (as
the minimal fix).
This made us wonder why we still have that code around when no current
host code supports the old transport: We have no idea
2017 Apr 20
2
[PATCH 1/1] s390/virtio: change maintainership
On 03/02/2017 05:08 PM, Christian Borntraeger wrote:
> Halil is doing a lot more work in the virtio area on s390 than I
> do. Let's reflect the reality in the maintainers file.
>
> Signed-off-by: Christian Borntraeger <borntraeger at de.ibm.com>
> Acked-by: Halil Pasic <pasic at linux.vnet.ibm.com>
> Acked-by: Cornelia Huck <cornelia.huck at de.ibm.com>
2017 Apr 20
2
[PATCH 1/1] s390/virtio: change maintainership
On 03/02/2017 05:08 PM, Christian Borntraeger wrote:
> Halil is doing a lot more work in the virtio area on s390 than I
> do. Let's reflect the reality in the maintainers file.
>
> Signed-off-by: Christian Borntraeger <borntraeger at de.ibm.com>
> Acked-by: Halil Pasic <pasic at linux.vnet.ibm.com>
> Acked-by: Cornelia Huck <cornelia.huck at de.ibm.com>
2017 Mar 02
2
[PATCH 0/1] virtio-ccw maintainership
Michael, Jason,
Halil is doing more work on virtio-ccw and virtio in general than I
do. I seem to be busy enough with the KVM/s390 maintainership.
So it is time to reflect reality in the maintainer file.
Lets start with the kernel.
Christian Borntraeger (1):
s390/virtio: change maintainership
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.7.4
2017 Mar 02
2
[PATCH 0/1] virtio-ccw maintainership
Michael, Jason,
Halil is doing more work on virtio-ccw and virtio in general than I
do. I seem to be busy enough with the KVM/s390 maintainership.
So it is time to reflect reality in the maintainer file.
Lets start with the kernel.
Christian Borntraeger (1):
s390/virtio: change maintainership
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.7.4
2014 Sep 22
1
[PATCH] virtio: unify config_changed handling
Replace duplicated code in all transports with a single wrapper in
virtio.c.
The only functional change is in virtio_mmio.c: if a buggy device sends
us an interrupt before driver is set, we previously returned IRQ_NONE,
now we return IRQ_HANDLED.
As this must not happen in practice, this does not look like a big deal.
See also commit 3fff0179e33cd7d0a688dab65700c46ad089e934
virtio-pci: do not
2014 Sep 22
1
[PATCH] virtio: unify config_changed handling
Replace duplicated code in all transports with a single wrapper in
virtio.c.
The only functional change is in virtio_mmio.c: if a buggy device sends
us an interrupt before driver is set, we previously returned IRQ_NONE,
now we return IRQ_HANDLED.
As this must not happen in practice, this does not look like a big deal.
See also commit 3fff0179e33cd7d0a688dab65700c46ad089e934
virtio-pci: do not
2010 Aug 24
4
[PATCH 1/3] S390: take a full byte as ext_param indicator
Currenty the ext_param field only distinguishes between "config change" and
"vring interrupt". We can do a lot more with it though, so let's enable a
full byte of possible values and constants to #defines while at it.
Signed-off-by: Alexander Graf <agraf at suse.de>
---
v1 -> v2:
- move defines to virtio_s390.h
---
arch/s390/include/asm/kvm_virtio.h | 6
2010 Aug 24
4
[PATCH 1/3] S390: take a full byte as ext_param indicator
Currenty the ext_param field only distinguishes between "config change" and
"vring interrupt". We can do a lot more with it though, so let's enable a
full byte of possible values and constants to #defines while at it.
Signed-off-by: Alexander Graf <agraf at suse.de>
---
v1 -> v2:
- move defines to virtio_s390.h
---
arch/s390/include/asm/kvm_virtio.h | 6
2008 Jun 03
12
[RFC 0/3]: hvc_console rework for platform without hard irqs
This patch set if my first attempt to make virtio_console usable on s390.
To do so, I had to change hvc_console, because s390 has no request_irq and
no free_irq.
I want to get feedback from the main users of hvc_console before I proceed.
The basic idea of this patch set is to remove the calls to request_irq and
free_irq and replace them with backend specific callbacks.
Please see the
2008 Jun 03
12
[RFC 0/3]: hvc_console rework for platform without hard irqs
This patch set if my first attempt to make virtio_console usable on s390.
To do so, I had to change hvc_console, because s390 has no request_irq and
no free_irq.
I want to get feedback from the main users of hvc_console before I proceed.
The basic idea of this patch set is to remove the calls to request_irq and
free_irq and replace them with backend specific callbacks.
Please see the
2017 Jul 04
4
[PATCH 0/1] Change email address
New employer, new address. Make sure people use the right one.
Christian, Martin, it's probably quickest if one of you takes this.
Cornelia Huck (1):
Update my email address
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
2.13.0
2017 Jul 04
4
[PATCH 0/1] Change email address
New employer, new address. Make sure people use the right one.
Christian, Martin, it's probably quickest if one of you takes this.
Cornelia Huck (1):
Update my email address
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
2.13.0
2010 Aug 23
3
[PATCH 1/2] S390: take a full byte as ext_param indicator
Currenty the ext_param field only distinguishes between "config change" and
"vring interrupt". We can do a lot more with it though, so let's enable a
full byte of possible values and constants to #defines while at it.
Signed-off-by: Alexander Graf <agraf at suse.de>
---
drivers/s390/kvm/kvm_virtio.c | 22 ++++++++++++++++------
1 files changed, 16 insertions(+), 6
2010 Aug 23
3
[PATCH 1/2] S390: take a full byte as ext_param indicator
Currenty the ext_param field only distinguishes between "config change" and
"vring interrupt". We can do a lot more with it though, so let's enable a
full byte of possible values and constants to #defines while at it.
Signed-off-by: Alexander Graf <agraf at suse.de>
---
drivers/s390/kvm/kvm_virtio.c | 22 ++++++++++++++++------
1 files changed, 16 insertions(+), 6
2008 May 21
1
[Fwd: [PATCH]: Fix silly output for virtio devices in /proc/interrupts]
(sent to the kvm list erroneously)
-------------- next part --------------
An embedded message was scrubbed...
From: Chris Lalancette <clalance at redhat.com>
Subject: [PATCH]: Fix silly output for virtio devices in /proc/interrupts
Date: Wed, 21 May 2008 14:51:45 +0200
Size: 4582
Url: http://lists.linux-foundation.org/pipermail/virtualization/attachments/20080521/38a29f92/attachment.eml