ALT Linux Sisyphus discussions
 help / color / mirror / Atom feed
From: Led <ledest@gmail.com>
To: ALT Linux Sisyphus discussions <sisyphus@lists.altlinux.org>
Subject: Re: [sisyphus] IQ: kernel-image-std-smp-2.6.24-alt0.3
Date: Wed, 27 Feb 2008 16:34:09 +0200
Message-ID: <200802271634.10093.ledest@gmail.com> (raw)
In-Reply-To: <20080227142325.GC20439@localhost.localdomain>

В сообщении от Wednesday 27 February 2008 16:23:25 вы написали:
> On [Wed, 27.02.2008 16:14], Led wrote:
> > В сообщении от Wednesday 27 February 2008 16:12:55 вы написали:
> > > On [Wed, 27.02.2008 15:55], Led wrote:
> > > > Не знаю из-за этого или нет, но qemu-kvm в сизифе принудительно
> > > > собран gcc4.1, а не gcc3.4
> > >
> > > Этого делать нельзя.
> > >
> > > > Could someone please explain the issue with gcc4, please?  Or point
> > > > me to an existing explanation?
> > >
> > > The issue is that gcc4 optimizes better, but this breaks assumptions of
> > > QEmu.
> > >
> > > Example: The basic idea (simplified!) of QEmu is writing C functions
> > > which implement the instructions of the target CPU. Then, code to be
> > > emulated is translated by chaining the _compiled_ functions
> > > (corresponding to the target code) together, but _leaving_ out the
> > > return instruction at the end of the function (otherwise, the resulting
> > > code would return already after the first emulated instruction).
> > >
> > > Now, gcc4 can produce code with several return instructions (with no
> > > option to turn that of, as far as I understand). You cannot cut them
> > > out, and therefore you cannot chain the simple functions.
> > >
> > > There seem to be other issues, too, like not being able to correctly
> > > link the user emulation code, but I am not that sure about it.
> >
> > qemu-kvm ничего практически не эмулирует, а использует аппаратную
> > виртуализацию, поэтому он только для запуска x84_64 и x86_32
>
> Аппаратной виртуализации подлежат все инструкции или часть всё же
> эмулируется средствами qemu?

AFAIK все

-- 
Led

  parent reply	other threads:[~2008-02-27 14:34 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 16:16 Valery V. Inozemtsev
2008-02-26 16:57 ` Led
2008-02-26 18:29   ` Valery V. Inozemtsev
2008-02-26 20:52     ` Michael Shigorin
2008-02-27  6:20       ` Valery V. Inozemtsev
2008-02-27  7:19         ` Valery V. Inozemtsev
2008-02-27 13:21       ` Mikhail Yakshin
2008-02-27 13:55         ` Led
2008-02-27 14:14             ` Led
2008-02-27 14:34                 ` Led [this message]
2008-02-27 16:29                   ` Damir Shayhutdinov
2008-02-27 14:15           ` Kirill A. Shutemov
2008-02-26 17:03 ` Sergey V Turchin
2008-02-26 18:15   ` Valery V. Inozemtsev
2008-02-27 11:30     ` Sergey V Turchin
2008-02-26 17:03 ` Pavlov Konstantin
2008-02-26 18:17   ` Valery V. Inozemtsev
2008-02-26 21:22     ` Pavlov Konstantin
2008-02-26 21:40       ` Led
2008-02-26 21:44         ` Mikhail Gusarov
2008-02-26 21:51           ` Led
2008-02-26 21:51             ` Mikhail Gusarov
2008-02-26 21:51         ` Pavlov Konstantin
2008-02-26 21:58           ` Pavlov Konstantin
2008-03-01 10:17             ` Michael Shigorin
2008-02-26 21:53         ` Dmitry V. Levin
2008-03-01 10:17         ` Michael Shigorin
2008-03-01 13:58           ` Led
2008-03-01 14:09             ` Dmitry V. Levin
2008-03-01 14:18               ` Led
2008-03-01 19:09             ` Michael Shigorin
2008-03-04 22:10       ` Konstantin A. Lepikhov
2008-02-26 17:18 ` Roman Savochenko
2008-02-26 18:18   ` Valery V. Inozemtsev
2008-02-26 20:59 ` Anton Farygin
2008-02-26 21:56   ` Dmitry V. Levin
2008-02-27  9:10     ` Anton Farygin
2008-02-27  9:19       ` Stanislav Ievlev
2008-02-27 13:45         ` Anton Farygin
2008-02-28  6:49           ` Stanislav Ievlev
2008-02-28 12:01             ` Anton Farygin
2008-02-27  6:25   ` Valery V. Inozemtsev

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=200802271634.10093.ledest@gmail.com \
    --to=ledest@gmail.com \
    --cc=sisyphus@lists.altlinux.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

ALT Linux Sisyphus discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/sisyphus/0 sisyphus/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 sisyphus sisyphus/ http://lore.altlinux.org/sisyphus \
		sisyphus@altlinux.ru sisyphus@altlinux.org sisyphus@lists.altlinux.org sisyphus@lists.altlinux.ru sisyphus@lists.altlinux.com sisyphus@linuxteam.iplabs.ru sisyphus@list.linux-os.ru
	public-inbox-index sisyphus

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.sisyphus


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git