All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Kohl <bernhard.kohl@nsn.com>
To: ext Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] pc: disable the BOCHS BIOS panic port
Date: Mon, 15 Nov 2010 17:17:56 +0100	[thread overview]
Message-ID: <4CE15D34.8030507@nsn.com> (raw)
In-Reply-To: <D57FF643-7385-464E-AC79-B9C1829D23E3@suse.de>

Am 15.11.2010 11:09, schrieb ext Alexander Graf:
> On 15.11.2010, at 10:53, Bernhard Kohl wrote:
>
>    
>> Am 01.09.2010 16:44, schrieb Bernhard Kohl:
>>      
>>> We have an OS which writes to port 0x400 when probing for special hardware.
>>> This causes an exit of the VM. With SeaBIOS this port isn't used anyway.
>>>
>>> Signed-off-by: Bernhard Kohl<bernhard.kohl@nsn.com>
>>> ---
>>>   hw/pc.c |    2 --
>>>   1 files changed, 0 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/hw/pc.c b/hw/pc.c
>>> index 69b13bf..3f81229 100644
>>> --- a/hw/pc.c
>>> +++ b/hw/pc.c
>>> @@ -430,8 +430,6 @@ static void bochs_bios_write(void *opaque, uint32_t addr, uint32_t val)
>>>           /* Bochs BIOS messages */
>>>       case 0x400:
>>>       case 0x401:
>>> -        fprintf(stderr, "BIOS panic at rombios.c, line %d\n", val);
>>> -        exit(1);
>>>       case 0x402:
>>>       case 0x403:
>>>   #ifdef DEBUG_BIOS
>>>
>>>        
>> Hi,
>>
>> could you please look at this?
>>      
> This patch makes that port that was silent before print debug output if DEBUG_BIOS is enabled which might be confusing.
>
> How about something like
>
> case 0x400:
> case 0x401:
>      /* used to be panic, now unused */
>      break;
>
>
> Alex
>
>
>    
Yes, you are right. I will take your proposal in patch v2.

Bernhard

      reply	other threads:[~2010-11-15 16:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-01 14:44 [Qemu-devel] [PATCH] pc: disable the BOCHS BIOS panic port Bernhard Kohl
2010-11-15  9:53 ` [Qemu-devel] " Bernhard Kohl
2010-11-15 10:09   ` Alexander Graf
2010-11-15 16:17     ` Bernhard Kohl [this message]

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=4CE15D34.8030507@nsn.com \
    --to=bernhard.kohl@nsn.com \
    --cc=agraf@suse.de \
    --cc=qemu-devel@nongnu.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.