From: Alexander Graf <agraf@suse.de>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Heinz Graalfs <graalfs@linux.vnet.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
Jens Freimann <jfrei@linux.vnet.ibm.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Einar Lueck <elelueck@de.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 2/3] geometry detection: use HDIO_GETGEO
Date: Wed, 02 May 2012 13:09:58 +0200 [thread overview]
Message-ID: <4FA11606.2000306@suse.de> (raw)
In-Reply-To: <4FA10C20.7050005@de.ibm.com>
On 05/02/2012 12:27 PM, Christian Borntraeger wrote:
> On 27/04/12 18:12, Paolo Bonzini wrote:
>> Il 26/04/2012 15:49, Christian Borntraeger ha scritto:
>>> +#ifdef __linux__
>>> + } else if (bdrv_ioctl(bs, HDIO_GETGEO,&geo) == 0) {
>>> + *pcyls = geo.cylinders;
>>> + *pheads = geo.heads;
>>> + *psecs = geo.sectors;
>>> + bdrv_set_geometry_hint(bs, *pcyls, *pheads, *psecs);
>>> +#endif
>> Perhaps you could instead move guess_disk_lchs to target-specific code,
>> adding add this code to the s390-specific implementation and under
>> #ifdef __s390__. For x86 it doesn't make much sense, because a disk's
>> geometry most likely will be a wrong guess for the geometry that a guest
>> (for guests that care at all about geometries).
> Fine with me. We care about the geometry only for dasd devices, Even for FCP-based
> SCSI devices on s390 the geometry is not relevant. So moving that part to
> s390 specific code might make sense if nobody else needs that.
> Is that the case?
> Alex, would that be ok for you?
As hinted in my other mail, I think the way to go would be to give a
hint to the geometry code that we're running on a DASD disk. Then we can
* Ask the host device if it can give us its geometry, if so, use it
* Guess depending on the logical block size
and everyone should be happy :). I would really like to have as little
#ifdef TARGET_S390 code in QEMU. And #ifdef __s390__ is even worse, as
it means we won't be able to execise that code path on other architectures.
Alex
next prev parent reply other threads:[~2012-05-02 11:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1335448165-26174-1-git-send-email-borntraeger@de.ibm.com>
[not found] ` <1335448165-26174-2-git-send-email-borntraeger@de.ibm.com>
[not found] ` <4F9AC55F.5000101@redhat.com>
2012-05-02 10:18 ` [Qemu-devel] [PATCH 1/3] Fix geometry sector calculation Christian Borntraeger
2012-05-02 10:25 ` Paolo Bonzini
2012-05-02 10:50 ` Christian Borntraeger
2012-05-02 11:05 ` Paolo Bonzini
2012-05-02 11:07 ` Alexander Graf
2012-05-02 11:09 ` Paolo Bonzini
2012-05-02 11:10 ` Alexander Graf
2012-05-02 11:23 ` Paolo Bonzini
[not found] ` <1335448165-26174-3-git-send-email-borntraeger@de.ibm.com>
[not found] ` <4F9AC55D.3000904@redhat.com>
2012-05-02 10:27 ` [Qemu-devel] [PATCH 2/3] geometry detection: use HDIO_GETGEO Christian Borntraeger
2012-05-02 11:09 ` Alexander Graf [this message]
2012-05-02 11:26 ` Paolo Bonzini
2012-05-02 11:35 ` Alexander Graf
2012-05-02 11:38 ` Paolo Bonzini
2012-05-02 12:54 ` Alexander Graf
2012-05-02 14:27 ` Christian Borntraeger
2012-05-02 15:05 ` Alexander Graf
2012-05-02 18:49 ` Christian Borntraeger
2012-05-02 15:57 ` Stefan Weinhuber
2012-05-02 18:39 ` Alexander Graf
2012-05-02 11:56 ` Christian Borntraeger
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=4FA11606.2000306@suse.de \
--to=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=elelueck@de.ibm.com \
--cc=graalfs@linux.vnet.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).