From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jan Kiszka <jan.kiszka@siemens.com>
Subject: extboot: Purpose of cmd value
Date: Thu, 18 Feb 2010 15:01:02 +0100
Message-ID: <4B7D481E.2090308@siemens.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Cc: kvm <kvm@vger.kernel.org>
To: Anthony Liguori <aliguori@us.ibm.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from david.siemens.de ([192.35.17.14]:19263 "EHLO david.siemens.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1755402Ab0BROBX (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 18 Feb 2010 09:01:23 -0500
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Hi Anthony,

I have to fix extboot for non-KVM usage which means pushing its
variables to writable RAM (probably some spare INT vector(s) in the
BASIC area).

In that process, I stumbled over the cmd value passed to extboot_init,
then stored in qemu_malloc'ed memory, and finally reported to the guest
side via port 0x404. It's constant so far, always 1. So there is quite a
bit unused code and data on both sides. Can we drop that?

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux