From: pebolle@tiscali.nl (Paul Bolle)
To: kernelnewbies@lists.kernelnewbies.org
Subject: booting kernel with kvm
Date: Wed, 15 Oct 2014 20:55:08 +0200 [thread overview]
Message-ID: <1413399308.2128.22.camel@x220> (raw)
In-Reply-To: <CADQxmtrq9MniLpo2JZWyeBef85N-LuQAXaRr3X9Fiw31pk5q6g@mail.gmail.com>
On Wed, 2014-10-15 at 23:27 +0530, harisha ja wrote:
> rama at ubuntu:~/linux/linux_ws$ git diff
> diff --git a/drivers/net/ethernet/intel/e1000/e1000_main.c
> b/drivers/net/ethernet/intel/e1000/e1000_main.c
> index cbc330b..3063991 100644
> --- a/drivers/net/ethernet/intel/e1000/e1000_main.c
> +++ b/drivers/net/ethernet/intel/e1000/e1000_main.c
> @@ -945,7 +945,8 @@ static int e1000_probe(struct pci_dev *pdev, const
>[...]
> struct pci_device_id *ent)
> u16 tmp = 0;
> u16 eeprom_apme_mask = E1000_EEPROM_APME;
> int bars, need_ioport;
> -
> +
> + printk(KERN_DEBUG "I can modify the Linux kernel!\n");
> /* do not allocate ioport bars when not needed */
> need_ioport = e1000_is_need_ioport(pdev);
> if (need_ioport) {
Two things come to mind:
- I don't think printk() at KERN_DEBUG level makes it to the console (by
default at least). Try KERN_ERR;
- do you actually run kvm (so, basically, qemu) with an emulated e1000
device?
Hope this helps,
Paul Bolle
next prev parent reply other threads:[~2014-10-15 18:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 9:31 booting kernel with kvm harisha ja
2014-10-15 10:17 ` Paul Bolle
2014-10-15 10:27 ` Paul Bolle
2014-10-15 17:50 ` harisha ja
2014-10-15 18:48 ` Paul Bolle
2014-10-15 10:23 ` Raghavendra
2014-10-15 17:57 ` harisha ja
2014-10-15 18:55 ` Paul Bolle [this message]
2014-10-15 19:13 ` Raghavendra
2014-10-18 17:36 ` harisha ja
2014-10-15 22:28 ` Bruno Guedes Souto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1413399308.2128.22.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.