All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: Rob Landley <rob@landley.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Two quick requests.
Date: Mon, 12 Feb 2007 17:45:18 +0000	[thread overview]
Message-ID: <200702121745.19103.paul@codesourcery.com> (raw)
In-Reply-To: <200702121227.47557.rob@landley.net>

> > If you really want to do this, do it properly. Make it an error to use a
> > ro image if the user [implicitly] requests rw access.
>
> If there's no middle ground between "silently misbehave" and "refuse to
> start if anything _might_ be wrong", then why does current qemu warn about
> the 1024 hz thing?

Even at 1024Hz qemu still misbehaves, especially on heavily loaded hosts. 
1024Hz is sufficient for most common operating systems most of the time, but 
many will run happily without it. e.g. many linux kernels only need 100 or 
250Hz.

Paul

  reply	other threads:[~2007-02-12 17:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 22:19 [Qemu-devel] Two quick requests Rob Landley
2007-02-09 22:27 ` Paul Brook
2007-02-09 22:33   ` Rob Landley
2007-02-09 22:33   ` Dan Shearer
2007-02-09 22:48     ` Paul Brook
2007-02-09 22:59       ` Ed Swierk
2007-02-09 23:06         ` Paul Brook
2007-02-10 15:37           ` Daniel Jacobowitz
2007-02-12 17:27           ` Rob Landley
2007-02-12 17:45             ` Paul Brook [this message]
2007-02-12 18:17             ` Jan Marten Simons
2007-02-10 11:53       ` CAP_NET_ADMIN (was Re: [Qemu-devel] Two quick requests.) Kevin F. Quinn
2007-02-10 15:11         ` Paul Brook
2007-02-12  9:49           ` Chris Friedhoff
2007-02-12 23:25 ` [Qemu-devel] QEMU and SMP Option on dual core processor Danny Chieh-Yao, Cheng

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=200702121745.19103.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rob@landley.net \
    /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.