I get this, across netconsole:
[17179569.184000] console handover: boot [earlyvga_f_0] - real [tty0]
wanna take a look at why there's cruft in bootconsole-name please?
-EFULL ;)
earlyvga is 8 chars. struct console-name is char[8]. No space left
for the trailing ´\0´, the cruft comes from
to last version: Rediffed against -rc3, adapted to mips
cleanups by Ralf, fixed udbg-immortal cmd line arg on powerpc.
Signed-off-by: Gerd Hoffmann [EMAIL PROTECTED]
Acked-by: Paul Mundt [EMAIL PROTECTED]
Acked-by: Ralf Baechle [EMAIL PROTECTED]
Cc: Andi Kleen [EMAIL PROTECTED]
Cc: Alan Cox [EMAIL
line
you get what you ask for, no matter whenever you apply the patch or not.
With the args above /dev/console is linked to /dev/ttyS1, which might
make gpm fail. Would be a gpm bug though.
cheers,
Gerd
--
Gerd Hoffmann [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line
srctree (scm tags such as
-hgchangeset) and objtree (config tag, -default, -pae, ...) and
find it quite useful. The login prompt usually includes $(uname -r), so
you easily see what kernel the machine runs at the moment ...
cheers,
Gerd
--
Gerd Hoffmann [EMAIL PROTECTED]
-
To unsubscribe from
?
There are range checks for both kernel (_text - _etext) and modules
(.text section). Anything outside isn't patched.
cheers,
Gerd
--
Gerd Hoffmann [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
;)
Changing that for x86 would break existing guests though.
cheers,
Gerd
--
Gerd Hoffmann [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Jeremy Fitzhardinge wrote:
If we're running under Xen, then there's no VT console. This results
in vc-vc_screenbuf_size == 0, which causes alloc_bootmem to panic.
Don't bother allocating a vc_screenbuf if its going to be 0 sized.
NAK.
The *real* problem is that the real-mode boot code never
with the earlyprintk and console mess ...
cheers,
Gerd
--
Gerd Hoffmann [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
from the boot console to the real console device works
smoothly.
The patch also changes the x86 early_printk code to use this. The early
console is simply tagged as boot console, the disable_early_printk()
call is gone as it isn't needed any more.
cheers,
Gerd
--
Gerd Hoffmann [EMAIL
it in -mm for a while to shake out any architecture issues which
might show up. Comments?
cheers,
Gerd
--
Gerd Hoffmann [EMAIL PROTECTED]
Fixes and cleanups for earlyprintk aka boot console.
The console subsystem already has an idea of a boot console, using the
CON_BOOT flag. The implementation
changes: there is just a small change needed to
make it build on !ppc, that should be identical identical in my (xen)
and rusty (lguest) patch series. Patching it only once is fine for
obvious reasons ;)
cheers,
Gerd
--
Gerd Hoffmann [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line
Avi Kivity wrote:
- new userspace interface (work in progress)
kvmfs in kvm-15 kernel code does not to build with older kernels (2.6.16
fails, 2.6.18 works ok), looks like the reason are some changes in
superblock handling.
Do you intend to fix that?
cheers,
Gerd
--
Gerd Hoffmann [EMAIL
The test which automatically enables the backup timer on some HP
machines doesn't trigger on other hardware which needs the backup
timer too.
This patch add a way to enable it manually (8250.use_backup_timer=1)
to deal with these machines.
Signed-off-by: Gerd Hoffmann [EMAIL PROTECTED]
Cc: Alex
Dave Jones wrote:
On Wed, Feb 28, 2007 at 11:23:46AM +0100, Gerd Hoffmann wrote:
The test which automatically enables the backup timer on some HP
machines doesn't trigger on other hardware which needs the backup
timer too.
Did you figure out *why* that test doesn't trigger?
I didn't
Andrew Morton wrote:
On Tue, 20 Feb 2007 12:35:49 +0100 Gerd Hoffmann [EMAIL PROTECTED] wrote:
It blows up on powerpc:
drivers/built-in.o(.init.text+0x2080): In function `.console_init':
: undefined reference to `.disable_early_printk'
Hmm, I think this is just a chunk being lost due
Jeremy Fitzhardinge wrote:
Gerd Hoffmann wrote:
Hmm, I think this is just a chunk being lost due to the clash with the
older version of the patch submitted as part of the xen series.
But I thought the old version I had posted was well and truly dropped.
Isn't this problematic patch the one
Paul Mackerras wrote:
Gerd Hoffmann writes:
This patch fixes the console selection code to *not* consider a boot
console a full-featured one, so the first non-boot console registering
will become the default console instead. This way the unregister call
for the boot console
-vmirom instead of xen-via-paravirt_ops reduces
the QA effort. You still have 5 Hypervisors you have to test against.
cheers,
Gerd
--
Gerd Hoffmann [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo
Ingo Molnar wrote:
* Gerd Hoffmann [EMAIL PROTECTED] wrote:
[using vmi rom]
IIRC there was some proof-of-concept at least for xen guests.
yes - but de-facto contradicted by the Xen paravirt_ops patches sent to
lkml ;)
Yep. The fact that it is possible to do that doesn't imply
Ingo Molnar wrote:
* Gerd Hoffmann [EMAIL PROTECTED] wrote:
Oh, and btw: What was the reason why kvm paravirtualization doesn't
use the vmi interface?
cleanliness and performance: KVM doesnt need any artificial indirection.
Xen doesn't need it either.
IMO the GPL-ed ROM portion of VMI
Avi Kivity wrote:
Gerd Hoffmann wrote:
Oh, and btw: What was the reason why kvm paravirtualization doesn't use
the vmi interface?
There actually was proof of concept code to do just that (by Anthony
Liguori). For Linux, I feel paravirt_ops is superior as we can extend
code by Anthony Liguori exists) and kill one more item on the
(linux) QA test matrix? (just following your arguments, not that I'm
confident it would actually help reducing QA effort).
cheers,
Gerd
--
Gerd Hoffmann [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe
a
straightforward technology-based migratory path out of the legacy.
See above, that path exists with Xen too.
cheers,
Gerd
--
Gerd Hoffmann [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
Muli Ben-Yehuda wrote:
On Wed, Nov 07, 2007 at 04:21:04PM +0200, Amit Shah wrote:
We make the dma_mapping_ops structure to point to our structure so
that every DMA access goes through us. (This is the reason this only
works for 64-bit guest. 32-bit guest doesn't yet have a dma_ops
struct.)
Maxim Levitsky wrote:
Will integrated sensors on DG965 motherboard be supported?
They can be accessed only through the
HECI interface, but the board has no AMT, and even if it had one, I don't
think AMT includes HW sensors.
While talking about AMT ...
ad
While talking about AMT: One quite
On 09/25/12 15:45, Greg KH wrote:
Hi all,
If you haven't sent me any pending patches for 3.7, it's a bit too late
as I've now closed the usb-next tree for any new stuff for 3.7, unless
it's bug fixes.
If you have sent me stuff and I've missed it, please let me know as I
think my queue is
On 11/05/12 19:19, Andy King wrote:
Hi David,
The big and only question is whether anyone can actually use any of
this stuff without your proprietary bits?
Do you mean the VMCI calls? The VMCI driver is in the process of being
upstreamed into the drivers/misc tree. Greg (cc'd on these
Andrew Morton wrote:
On Thu, 20 Sep 2007 18:28:49 +0100 (BST) Maciej W. Rozycki [EMAIL
PROTECTED] wrote:
Move the hadover message to after the boot console has been released to
avoid bad interactions between it and the real console.
[ longish problem discussion snipped ]
considered
Russell King wrote:
I had an issue with the console initialisation on serial ports, which I
discovered during my PXA work. My reason for asking about the kernel
versions (which Andrew forwarded to LKML) is to determine whether the
report is as a result of those changes, or lack of those
Scott wrote:
On Sat, 2007-10-06 at 12:48 -0600, Robert Hancock wrote:
Oct 2 21:59:32 htpc cx88[0]: irq mpeg [0x8] pci_abort*
Oct 2 21:59:32 htpc cx88[0]/2-mpeg: general errors: 0x0008000
I assumed it was an interrupt issue based on the 'irq mepg' error, not a
DMA issue.
It's a DMA
Robin Getz wrote:
I was putting together an early printk implementation for the Blackfin, and
was wondering what the expected behaviour was in this situation.
When I set up my bootargs earlyprintk=serial,ttyBF0,57600 and have no console
defined (no graphical console, no serial console).
Mike Frysinger wrote:
Hmm, sort of, although I didn't think about the case of no real console
replacing the early console. The intention of the patch is to have a
smooth handover from the boot console to the real console. And, yes, if
no real console is ever registered the boot console keeps
Robin Getz wrote:
Hmm, yes, should be doable in generic code. Check whenever the current
console has CON_BOOT set and if so unregister it.
Something like:
+++ kernel/printk.c (working copy)
+int __init disable_boot_consoles(void)
+{
+ struct console *con;
+
+ for
Robin Getz wrote:
Try #3...
From: Robin Getz [EMAIL PROTECTED]
+static int __init disable_boot_consoles(void)
+{
+ printk(KERN_INFO here\n);
leftover debug printk?
cheers,
Gerd
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
[EMAIL PROTECTED]
CC: Gerd Hoffmann [EMAIL PROTECTED]
Acked-by: Gerd Hoffmann [EMAIL PROTECTED]
cheers,
Gerd
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 04/11/13 11:29, Stefan Hajnoczi wrote:
On Mon, Apr 08, 2013 at 12:27:06PM +, Zhanghaoyu (A) wrote:
On Sun, Apr 07, 2013 at 04:58:07AM +, Zhanghaoyu (A) wrote:
I start a kvm VM with vnc(using the zrle protocol) connect, sometimes
qemu program crashed during starting period, received
On 02/07/13 01:23, Andy King wrote:
+struct vsock_transport_recv_notify_data {
+ u64 data1; /* Transport-defined. */
+ u64 data2; /* Transport-defined. */
+ bool notify_on_block;
+};
+
+struct vsock_transport_send_notify_data {
+ u64 data1; /* Transport-defined. */
+
On 02/07/13 01:23, Andy King wrote:
Hi,
+/* Option name for socket's service label. Use as the option name in
+ * setsockopt(3) or getsockopt(3) to set or get the service label for a
socket.
+ * The service label is a C-style NUL-terminated string. Only available for
+ * hypervisor
On 02/12/13 16:21, Andy King wrote:
Hi Gerd,
+struct vsock_transport {
...
Whoa. This has grown *alot*. Care to explain this please? Patch
creating a Documentation/virtual/vsock.txt would be cool.
Yes, it grew because of the notification stuff, which I'd forgotten
about until I
On 02/07/13 01:23, Andy King wrote:
+static int vsock_create(struct net *net, struct socket *sock,
+ int protocol, int kern)
+{
+ if (!sock)
+ return -EINVAL;
+
+ if (protocol)
+ return -EPROTONOSUPPORT;
+
IMO protocol == PF_VSOCK
Hi,
Unlike previous submissions, where the new socket family was entirely reliant
on VMware's VMCI PCI device (and thus VMware's hypervisor), VM Sockets is now
*completely* separated out into two parts, each in its own module:
Some separation still needs to be done:
CC [M]
Hi,
Likewise, I expect with the final version vmci_transport is a
separate module (or moves into the vmci driver), correct?
When you say final, do you mean something that we have to do before
acceptance into mainline or something we can refine over time?
IMHO refining in-tree is fine.
Hi,
diff --git a/net/vmw_vsock/Kconfig b/net/vmw_vsock/Kconfig
new file mode 100644
index 000..95e2568
--- /dev/null
+++ b/net/vmw_vsock/Kconfig
@@ -0,0 +1,14 @@
+#
+# Vsock protocol
+#
+
+config VMWARE_VSOCK
+ tristate Virtual Socket protocol
+ depends on VMWARE_VMCI
e085c81d3fc95a7e2e938deec65843ba7c00afe3 Mon Sep 17 00:00:00 2001
From: Gerd Hoffmann kra...@redhat.com
Date: Wed, 13 Feb 2013 18:00:19 +0100
Subject: [PATCH 2/4] af_vsock: don't overwrite sock-state
We set sock-state to SS_CONNECTING before calling the transport,
no need to do that again afterwards, thereby overwriting any
updates
On 02/07/13 01:23, Andy King wrote:
+ written = transport-stream_enqueue(
+ vsk, msg-msg_iov,
+ len - total_written);
Hmm, shouldn't we pass total_written to stream_enqueue here?
In case a blocking send(big-buffer) call gets
On 02/07/13 01:23, Andy King wrote:
+/* Use this as the destination CID in an address when referring to the
+ * hypervisor. VMCI relies on it being 0, but this would be useful for other
+ * transports too.
+ */
+
+#define VMADDR_CID_HYPERVISOR 0
+
+/* This CID is specific to VMCI and can
On 02/18/13 18:07, Andy King wrote:
Hi Gerd,
+ written = transport-stream_enqueue(
+ vsk, msg-msg_iov,
+ len - total_written);
Hmm, shouldn't we pass total_written to stream_enqueue here?
In case a blocking send(big-buffer)
is also worth a try. Some modules are
loaded nevertheless (usb + hid stuff, so you can login with a usb kbd
for example), but most of them are not yet loaded ...
cheers,
Gerd
--
Gerd Hoffmann [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
Jan Engelhardt wrote:
On Jan 29 2007 09:30, Gerd Hoffmann wrote:
Bernhard Walle wrote:
* Jan Engelhardt [EMAIL PROTECTED] [2007-01-27 15:53]:
brokenmodules=..., but that's SUSE's linuxrc.
good enough to boot the rescue system from the install cd without
oopsing and fix up the blacklist file
Hi,
We have a DMA32 zone now, lets use it to make sure the card
can reach the memory we have allocated for the video frame
buffers.
please apply,
Gerd
Fix bttv and friends on 64bit machines with lots of memory.
We have a DMA32 zone now, lets use it to make sure the card
can reach the
at least give an idea how it
works, not sure you can actually reuse the code. Chances are not too
bad though, it is used not only for video buffers, but also for audio
and mpeg2 data, so it could be generic enough to fit your needs too.
cheers,
Gerd
--
Gerd Hoffmann [EMAIL PROTECTED]
-
To unsubscribe
--
Gerd Hoffmann [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Hi,
Jumping in here, looks like this could develop into a direction useful
for Xen.
Background: Xen has a mechanism called grant tables for page sharing.
Guest #1 can issue a grant for another guest #2, which in turn then
can use that grant to map the page owned by guest #1 into its address
Hi,
That would render the notifies useless for Xen too. Xen needs to
intercept the actual pte clear and instead of just zapping it use the
hypercall to do the unmap and release the grant.
We are tackling that by having our own page table hanging off the
structure representing our seg
Andrea Arcangeli wrote:
Like Avi said, Xen is dealing with the linux pte only, so there's no
racy smp page fault to serialize against. Perhaps we can add another
notifier for Xen though.
But I think it's still not enough for Xen to have a method called
before the ptep_clear_flush: rmap.c
Avi Kivity wrote:
You are
probably better off designing something that is PV specific instead of
shoehorning it in to fit a different model (at least for the things I
have in mind).
Well, if we design our pv devices to look like hardware, they will fit
quite well. Both to the guest OS
+/*
+ * Guest has page alignment and padding requirements. At the host, it will
+ * only lead to wasted space at the vcpu struct. For this reason, the struct
+ * is not anonymous
+ */
+union kvm_hv_clock {
+ struct kvm_hv_clock_s {
+ u64 tsc_mult;
+ u64 now_ns;
On 01/09/13 03:22, Dmitry Torokhov wrote:
On Tue, Jan 08, 2013 at 05:46:01PM -0800, David Miller wrote:
I'd much rather see a hypervisor neutral solution than a hypervisor
specific one which this certainly is.
Objectively speaking neither solution is hypervisor neutral as there are
Jeff Garzik wrote:
Christoph Hellwig wrote:
And this is really dumb. autotools is a completely pain in the ass and
not useful at all for linux-only tools.
A myth. It is quite useful for packagers, because of the high Just
Works(tm) factor. After porting an entire across several revisions
Joel Becker wrote:
On Fri, Jul 06, 2007 at 11:01:07AM +0200, Gerd Hoffmann wrote:
And the 10% where it doesn't work it is a real pain to figure what goes
wrong due to the completely unreadable Makefiles generated by autotools.
After all they are not Makefiles, they are shellscripts embedded
Using a Nova-T dvb card, I get the following in /var/log/messages...
22:09:54 kernel: cx88_wakeup: 2 buffers handled (should be 1)
...every few seconds while watching TV with xine or other dvb-apps. The
event results in a visible interruption of the video stream.
I've added the printk some
Renato S. Yamane wrote:
Sasa Ostrouska escreveu:
** Short intro for the impatient: Just use vga=ask for the first time,
** enter `scan' on the video mode prompt, pick the mode you want to use,
** remember its mode ID (the four-digit hexadecimal number) and then
** set the vga parameter to
.
Checking video mode field only to see whenever SCREEN_INFO is
initialized is not enougth, in some cases it is zero although
a vga card is present. Lets additionally check cols and lines.
Signed-off-by: Gerd Hoffmann [EMAIL PROTECTED]
Cc: Rusty Russell [EMAIL PROTECTED]
Cc: Andi Kleen [EMAIL PROTECTED
Refine SCREEN_INFO sanity check for vgacon initialization.
Checking video mode field only to see whenever SCREEN_INFO is
initialized is not enougth, in some cases it is zero although
a vga card is present. Lets additionally check cols and lines.
Signed-off-by: Gerd Hoffmann [EMAIL PROTECTED]
Cc: Rusty
Yinghai Lu wrote:
Gerd's patch (console handover) was merged into mainline. it will
switch from early_printk to normal console in register_console via
CON_BOOT flags.. === only for x86
Tagging boot consoles (aka early_printk) with CON_BOOT certainly makes
sense. Just doing that doesn't work
Jeremy Fitzhardinge wrote:
Eric W. Biederman wrote:
I have several ideas on how we can make this work but first I have to
ask what is it that you are trying to accomplish?
The requirements are:
1. the domain builder needs to get various information about the
guest kernel by
Hi,
Gerd, in change 11196:b85da7cd9ea5 front: Fix rx buffer leak when
tearing down an interface. you added a call to
add_id_to_freelist(np-rx_skbs, id);. However, rx_skbs doesn't have
an extra entry for the list head, and there's never any corresponding
get_id_from_freelist(np-rx_skbs).
Jeremy Fitzhardinge wrote:
Gerd Hoffmann wrote:
Gerd, in change 11196:b85da7cd9ea5 front: Fix rx buffer leak when
tearing down an interface. you added a call to
add_id_to_freelist(np-rx_skbs, id);. However, rx_skbs doesn't have
an extra entry for the list head, and there's never any
Christoph Hellwig wrote:
On Thu, May 03, 2007 at 09:33:43AM +0200, Gerd Hoffmann wrote:
Guess so. It defaults to flip. I simplified the rx_copy/flip module
parameter to a simple rx_mode=0/1, but this is preserved from the
original. My guess is that originally there was only flip, and copy
xhci streams support is fixed, unblock usb attached scsi.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
drivers/usb/storage/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/storage/Kconfig b/drivers/usb/storage/Kconfig
index 8470e1b..4761a28 100644
of status pipe transfer errors.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
drivers/usb/storage/uas.c | 50 +++
1 file changed, 42 insertions(+), 8 deletions(-)
diff --git a/drivers/usb/storage/uas.c b/drivers/usb/storage/uas.c
index 3cf5a5f..f049038
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
drivers/usb/storage/uas.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/usb/storage/uas.c b/drivers/usb/storage/uas.c
index d966b59..fc08ee9 100644
--- a/drivers/usb/storage/uas.c
+++ b/drivers/usb/storage/uas.c
@@ -85,6 +85,8
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
drivers/usb/storage/uas.c | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/drivers/usb/storage/uas.c b/drivers/usb/storage/uas.c
index f049038..046eedf 100644
--- a/drivers/usb/storage/uas.c
+++ b/drivers
the radix tree. It can
both insert and remove ring segments. It loops over the segment list
and handles all segments instead of just the first. It is called
whenever an update is needed: When allocating a ring, when expanding
a ring and when releasing a ring.
Signed-off-by: Gerd Hoffmann kra
Simplifies locking, we'll protect the list with the device spin lock.
Also plugs races which can happen when two devices operate on the
global list.
While being at it rename the list head from list to work, preparing
for the addition of a second list.
Signed-off-by: Gerd Hoffmann kra
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
drivers/video/hyperv_fb.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/video/hyperv_fb.c b/drivers/video/hyperv_fb.c
index 8d456dc..130708f 100644
--- a/drivers/video/hyperv_fb.c
+++ b/drivers/video/hyperv_fb.c
@@ -575,6
is that the xorg vesa driver will not attach to the
device and thus the Xorg server will automatically use the fbdev
driver instead.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
drivers/video/hyperv_fb.c | 40 +++-
1 file changed, 39 insertions(+), 1
On Mi, 2013-10-02 at 14:29 +, KY Srinivasan wrote:
This patch adds a pci stub driver to hyper-fb. The hyperv framebuffer
driver will bind to the pci device then, so linux kernel and userspace
know there is a proper kernel driver for the device active. lspci shows
this for example:
On Di, 2013-09-17 at 13:30 -0700, Christoph Hellwig wrote:
On Fri, Sep 13, 2013 at 01:27:12PM +0200, Gerd Hoffmann wrote:
Simplifies locking, we'll protect the list with the device spin lock.
Also plugs races which can happen when two devices operate on the
global list.
While being
() and
radix_tree_preload_end() calls around the radix tree insert, since we
can now insert entries in interrupt context. There are now two helper
functions to make the code cleaner, and those functions are moved to
make them static.]
Signed-off-by: Gerd Hoffmann kra...@redhat.com
Signed-off-by: Hans de Goede hdego
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
drivers/hv/vmbus_drv.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
index b37c91b..2352ae48 100644
--- a/drivers/hv/vmbus_drv.c
+++ b/drivers/hv/vmbus_drv.c
@@ -899,10 +899,12 @@ static
Remove firmware framebuffer before initializing hyperv-fb. Needed
on gen2 virtual machines. Letting register_framebuffer handle the
switchover results in efifb still being active while hyperv graphics
are initialized, which in turn can make the linux kernel hang.
Signed-off-by: Gerd Hoffmann
From: K. Y. Srinivasan k...@microsoft.com
On Gen2 firmware, Hyper-V does not emulate the PCI bus. However, the MMIO
information is packaged up in DSDT. Extract this information and export it
for use by the synthetic framebuffer driver. This is the only driver that
needs this currently.
In this
support for it.
Based on a patch by Haiyang Zhang haiya...@microsoft.com
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
drivers/video/hyperv_fb.c | 86 +--
1 file changed, 60 insertions(+), 26 deletions(-)
diff --git a/drivers/video/hyperv_fb.c b
Use a resource for the hyperv mmio region instead of start/size
variables. Register the region properly so it shows up in
/proc/iomem.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
drivers/hv/vmbus_drv.c | 16 ++--
include/linux/hyperv.h | 3 +--
2 files changed, 11 insertions
initialization is in progress. This patch is
new in v2 and it fixes the hang listed as known issue in v1 of this
patch series.
please apply,
Gerd
Gerd Hoffmann (4):
vmbus: add missing breaks
vmbus: use resource for hyperv mmio region
hyperv-fb: add support for generation 2 virtual machines.
hyperv
On Mo, 2014-02-24 at 13:42 +0300, Dan Carpenter wrote:
I'm sorry, I know it sucks to not get credit for fixes, but please just
fold this into [patch 1/5]. We really should have a tag for this kind
of thing.
It's not because of the credits, but because Greg picked up #1 into one
of his
Remove firmware framebuffer before initializing hyperv-fb. Needed
on gen2 virtual machines. Letting register_framebuffer handle the
switchover results in efifb still being active while hyperv graphics
are initialized, which in turn can make the linux kernel hang.
Signed-off-by: Gerd Hoffmann
Use a resource for the hyperv mmio region instead of start/size
variables. Register the region properly so it shows up in
/proc/iomem.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
drivers/hv/vmbus_drv.c | 16 ++--
include/linux/hyperv.h | 3 +--
2 files changed, 11 insertions
support for it.
Based on a patch by Haiyang Zhang haiya...@microsoft.com
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
drivers/video/hyperv_fb.c | 86 +--
1 file changed, 60 insertions(+), 26 deletions(-)
diff --git a/drivers/video/hyperv_fb.c b
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
drivers/hv/vmbus_drv.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
index b37c91b..2352ae48 100644
--- a/drivers/hv/vmbus_drv.c
+++ b/drivers/hv/vmbus_drv.c
@@ -899,10 +899,12 @@ static
. This patch is
new in v2 and it fixes the hang listed as known issue in v1 of this
patch series.
v3 changes:
- fix a error handling bug in patch #3.
- don't include 90f3453585479d5beb75058da46eb573ced0e6ac
to avoid confusion
please apply,
Gerd
Gerd Hoffmann (4):
vmbus: add missing breaks
vmbus
cirrus kms driver lacks power management support, thus
the vga display doesn't work any more after S3 resume.
Fix this by adding suspend and resume functions.
Also make the mode_set function unblank the screen.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
drivers/gpu/drm/cirrus
bochs kms driver lacks power management support, thus
the vga display doesn't work any more after S3 resume.
Fix this by adding suspend and resume functions.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
drivers/gpu/drm/bochs/bochs.h | 1 +
drivers/gpu/drm/bochs/bochs_drv.c | 44
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
drivers/gpu/drm/bochs/bochs.h | 2 --
drivers/gpu/drm/bochs/bochs_fbdev.c | 1 -
2 files changed, 3 deletions(-)
diff --git a/drivers/gpu/drm/bochs/bochs.h b/drivers/gpu/drm/bochs/bochs.h
index 4608205..7eb52dd 100644
--- a/drivers/gpu/drm
the framebuffer isn't used
any more while hyperv-fb initialization is in progress.
v4 changes:
- use KBUILD_MODNAME everywhere for consistent naming.
- drop the two patches which Greg has staged in char-misc.
please apply,
Gerd
Gerd Hoffmann (2):
hyperv-fb: add support for generation 2 virtual
support for it.
Based on a patch by Haiyang Zhang haiya...@microsoft.com
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
drivers/video/hyperv_fb.c | 86 +--
1 file changed, 60 insertions(+), 26 deletions(-)
diff --git a/drivers/video/hyperv_fb.c b
Remove firmware framebuffer before initializing hyperv-fb. Needed
on gen2 virtual machines. Letting register_framebuffer handle the
switchover results in efifb still being active while hyperv graphics
are initialized, which in turn can make the linux kernel hang.
Signed-off-by: Gerd Hoffmann
Hi,
diff --git a/drivers/video/hyperv_fb.c b/drivers/video/hyperv_fb.c index
b7b3dd0..1b11886 100644
--- a/drivers/video/hyperv_fb.c
+++ b/drivers/video/hyperv_fb.c
@@ -683,6 +683,7 @@ static int hvfb_getmem(struct fb_info *info)
info-apertures-ranges[0].base =
.
please apply,
Gerd
Gerd Hoffmann (2):
hyperv-fb: add support for generation 2 virtual machines.
hyperv-fb: kick off efifb early
drivers/video/hyperv_fb.c | 88 +--
1 file changed, 62 insertions(+), 26 deletions(-)
--
1.8.3.1
--
To unsubscribe
1 - 100 of 1677 matches
Mail list logo
