All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com>
To: keir.fraser@eu.citrix.com, xen-devel@lists.xensource.com
Subject: [PATCH] hvmloader: Fix Parsing Etherboot Roms to Avoid Infinite Loop
Date: Wed, 09 Apr 2008 15:37:37 +0900	[thread overview]
Message-ID: <47FC6431.30903@ab.jp.nec.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 252 bytes --]

Hi,

The new etherboot parsing, introduced in cs 17372, causes an infinite
loop when the HVM guest has a vif device other than rtl8139.
The attached patch will fix this problem.

Regards,
-----------------------
Yosuke Iwamatsu
        NEC Corporation

[-- Attachment #2: fix_parse_etherboot.patch --]
[-- Type: all/allfiles, Size: 786 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

             reply	other threads:[~2008-04-09  6:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09  6:37 Yosuke Iwamatsu [this message]
2008-04-09  8:44 ` [PATCH] hvmloader: Fix Parsing Etherboot Roms to AvoidInfinite Loop Li, Haicheng

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=47FC6431.30903@ab.jp.nec.com \
    --to=y-iwamatsu@ab.jp.nec.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.