xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Michal Novotny <minovotn@redhat.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [PATCH] Fix restore handling checks
Date: Wed, 23 Jun 2010 14:12:30 +0200	[thread overview]
Message-ID: <4C21FA2E.3070807@redhat.com> (raw)
In-Reply-To: <19489.63562.359937.534740@mariner.uk.xensource.com>

On 06/23/2010 02:04 PM, Ian Jackson wrote:
> Michal Novotny writes ("Re: [PATCH] Fix restore handling checks"):
>    
>> Are you saying that it's OK for administrators to violate the IDE specs
>> and do it the way that is should never be done since this way it's not
>> working on bare-metal systems ? This is the breach and it shouldn't be
>> done this way so why to allow it? Shouldn't we care the code complies
>> with the specifications to have it done the right way?
>>      
> The job of the programmer is to give effect to the wishes of the
> users, not to comply with rules from elsewhere.  If the wishes of the
> users conflict with rules from elsewhere, including specs, then the
> programmer should do what the user wants.
>
> Ian.
>    
Right but I don't think someone uses the read-only IDE drives or 
read-only drives in general - at least for HVM guests since just few 
days I posted the patch to disallow write to the read-only devices on 
ioemu - maybe you remember I did post the patch at [1]. Before this 
patch applied the read-only disks were treated as read-write always no 
matter what the state of disk device was present in the xenstore so why 
not to teach the users the right things according to the specs. This 
shouldn't break anything if you consider you added my patch to xen-ioemu 
just 13 days ago and I find it rather confusing to let users define 
read-only IDE disks which is not right according to the specs, this 
means that by allowing it we could confuse the users so that they can 
think that read-only IDE disks does exists even according to the specs 
and they may try to think that the bare-metal IDE disks does support it 
as well. Since this shouldn't break anything why shouldn't we do the 
things the right way? They have SCSI disks and PV drivers if they want 
read-only disks after all.

Michal

[1] 
http://xenbits.xensource.com/gitweb?p=qemu-xen-unstable.git;a=commit;h=6392763643311272590ef5c6f75ba11d5b132585

-- 
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat

  parent reply	other threads:[~2010-06-23 12:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21 16:30 [PATCH] Fix restore handling checks Michal Novotny
2010-06-21 18:04 ` Keir Fraser
2010-06-22  5:43   ` Michal Novotny
2010-06-22  6:11     ` Michal Novotny
2010-06-22  6:14       ` Keir Fraser
2010-06-22  6:17         ` Michal Novotny
2010-06-22 12:56           ` Michal Novotny
2010-06-22 14:10             ` Konrad Rzeszutek Wilk
2010-06-23 11:27               ` Michal Novotny
2010-06-22 20:46             ` Dan Magenheimer
2010-06-23  9:59               ` Michal Novotny
2010-06-23 11:21               ` Michal Novotny
2010-06-23 13:51                 ` Dan Magenheimer
2010-06-23 14:14                   ` Michal Novotny
2010-06-22 14:56     ` Ian Jackson
2010-06-23 11:19       ` Paolo Bonzini
2010-06-23 11:27         ` Ian Jackson
2010-06-23 11:29           ` Michal Novotny
2010-06-23 11:50             ` Ian Jackson
2010-06-23 11:54               ` Michal Novotny
2010-06-23 12:04                 ` Ian Jackson
2010-06-23 12:10                   ` Paolo Bonzini
2010-06-23 12:20                     ` Michal Novotny
2010-06-23 12:20                     ` Michal Novotny
2010-06-23 12:12                   ` Michal Novotny [this message]
2010-06-23 12:33                   ` Alan Cox
2010-06-23 15:12                     ` George Dunlap
2010-06-23 16:26                     ` Dan Magenheimer
2010-06-23 12:35             ` Alan Cox
2010-06-23 12:37               ` Michal Novotny

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=4C21FA2E.3070807@redhat.com \
    --to=minovotn@redhat.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=pbonzini@redhat.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 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).