In message: <[EMAIL PROTECTED]>
Johannes Schindelin <[EMAIL PROTECTED]> writes:
: > I personally don't like tcl as a language, and prefer to code in C++ for
: > efficiency.
:
: Hmmm. "C++" and "efficiency" _does_ constitute a contradiction. Just think
: "operator+()". Honestly, the m
Thiemo Seufer wrote:
...
I recommend to go for a sufficiently flexible interface first, and then
introduce it gradually in all appropriate places. A macro like:
MIPS_OPC(ISA, ASE, CPU)
which compares the arguments with the currently selected CPU emulation
and throws an RI exception if the featu
Fabrice Bellard wrote:
Dirk Behme wrote:
Fabrice Bellard wrote:
Each machine can add specific support for that (for example a -cpu
option). It is likely to come at least for the PC machines.
I add suggest one more parameter to cpu_mips_set_model() to specify
optional features. A function c
Hi,
On Sat, 8 Jul 2006, Chris Wilson wrote:
> I personally don't like tcl as a language, and prefer to code in C++ for
> efficiency.
Hmmm. "C++" and "efficiency" _does_ constitute a contradiction. Just think
"operator+()". Honestly, the most inefficient code I saw was done in C++.
You really
Hi Luca,
Not wishing to start an argument, just to learn:
On Wed, 5 Jul 2006, Luca Barbato wrote:
The library is incompatible with itself depending on the configure time
options (see string constructors vs unicode string constructors)
It's perfectly possible to write code that compiles and w
Hi,
Can I add code to model additional hardware in Qemu?
Specifically, I want to add a tracing module that
dumps out the virtual and physical address of the
executing program's instruction and data accesses. (I
can't figure out if Qemu models the mmu)
Thanx
On Fri, 07 Jul 2006 10:07:47 +0200, G Portokalidis wrote:
> Actually, i have also noticed this.
> It implies that an exploit might not succeed (this usually the case with
> most exploits), since the attacker supplied shellcode will not be at the
> "expected" location.
>
> My question is, does any
When I had installed qemu(Host OS: win98),I execute qemumenu.bat.Unfortunately,qemumenu.bat shows lots of error messages,as follows:
>Bad command or file name>Bad command or file name>Invalid directory>Syntax error>Syntax error>Bad command or file name>Syntax error>QEMU_BIOS_DIR=>Bad command or
On Friday 07 July 2006 17:31, Palleni, F. - Franco - wrote:
> Hi to All,
>
> i'm writing to propose a feature, I would like to insert in qemu
> machine some hardware installed in host PC like a frame grabber, or
> other special hardware. How do you thimk about this features? it sould
> be imp
Hi to All,
i'm writing to propose a feature, I would like to insert in qemu
machine some hardware installed in host PC like a frame grabber, or
other special hardware. How do you thimk about this features? it sould
be implemented like kemu accelerator or somting like that.
Regards
Franco
Maybe there are some further issues in your setup. Could you please
provide more detailed kernel messages (regarding the panic)?
Thanks,
Jo.
maestro wrote:
hello just tested the patch against 0.8.1 and current cvs and at least
here it does not work:
still
Kernel panic - not syncing: Attempted
On Fri, 2006-07-07 at 11:00 -0400, WaxDragon wrote:
> It's a nice idea, but awfully *nix specific. ;0)
True, but it could be supplemented by the same idea when a user presses
the close button on the gui window. That could work on all versions.
--
Martin.
_
It's a nice idea, but awfully *nix specific. ;0)
On 7/7/06, Martin Garton <[EMAIL PROTECTED]> wrote:
Hi,
Now that ACPI is supported, does anyone agree that it would make sense
to trap SIGINT (any perhaps SIGTERM) and use it to generate an acpi
power button event? That way, operating systems th
赵刚 wrote:
> When I use qemu,I encouner these error messages,as follows:
> "
> C:\Program Files\Qemu>qemu BL3.4-qemu.img
> Could not open '\\.\kqemu' - QEMU acceleration layer not activated
> qemu: could not load PC bios '/c/Program Files/Qemu/bios.bin'
> "
> In fact, the directory (C:\Program Files
Hi,
Now that ACPI is supported, does anyone agree that it would make sense
to trap SIGINT (any perhaps SIGTERM) and use it to generate an acpi
power button event? That way, operating systems that support it could
shut down cleanly.
This would be particularly useful when you have multiple qemu in
When I use qemu,I encouner these error messages,as follows:"C:\Program Files\Qemu>qemu BL3.4-qemu.imgCould not open '\\.\kqemu' - QEMU acceleration layer not activatedqemu: could not load PC bios '/c/Program Files/Qemu/bios.bin'" In fact, the directory (C:\Program Files\Qemu) has the file:bios.bi
Try
zcat mwait.diff.gz | patch -p0
in the source directory.
Am 07.07.2006 um 14:57 schrieb maestro:
btw: when i patch < mwait.diff in the qemu-src directory patch cannot
find the files to patch and asks me for their location - did i do
anything wrong?
--
Joachim Henke
http://he-jo.net/
_
The last patch I sent, enabled the MONITOR cpuid flag for testing
purposes. So Linux guests won't execute the 'hlt' instruction
anymore. Since we don't really emulate an 'mwait' instruction, this
leads to high cpu usage on the host, even when the guest cpu is idle.
Please use the updated pa
Am Freitag, den 07.07.2006, 14:30 +0200 schrieb Joachim Henke:
> Could you please check, if the attached patch works for you? A quick
> test showed that Linux boots fine with the MONITOR flag set now.
>
> This patch adds 'monitor' and 'mwait' as nops, as suggested by Fabrice.
>
hello just teste
Could you please check, if the attached patch works for you? A quick
test showed that Linux boots fine with the MONITOR flag set now.
This patch adds 'monitor' and 'mwait' as nops, as suggested by Fabrice.
Regards,
Jo.
Am 06.07.2006 um 17:13 schrieb R. Armiento:
Uncompressing Linux... Ok, b
R. Armiento wrote:
The error looks very similar to the one reported here:
http://www.mail-archive.com/qemu-devel@nongnu.org/msg03964.html
But I believe that reported issue should not appear in recent qemu,
since SSE3 is now emulated (right?). (At least the patch in the end of
that thread see
It seems to me that AXFS (Advanced XIP File System) could be useful
for Linux guest under QEMU.
-Nigel
begin:vcard
fn:Nigel Horne
n:Horne;Nigel
org:NJH Music
email;internet:[EMAIL PROTECTED]
tel;fax:+44 870 705 9334
note:Skype: nigelhorne
x-mozilla-html:FALSE
version:2.1
end:vcard
__
On Fri, Jul 07 2006, Joachim Henke wrote:
> Yes, this patch was included, but it doesn't solve that problem. As
> this message [http://www.mail-archive.com/qemu-devel@nongnu.org/
> msg03972.html] states, the 'monitor' and the 'mwait' instructions
> have not been added. But your guest OS assume
Yes, this patch was included, but it doesn't solve that problem. As
this message [http://www.mail-archive.com/qemu-devel@nongnu.org/
msg03972.html] states, the 'monitor' and the 'mwait' instructions
have not been added. But your guest OS assumes them to be present,
because your host cpu has
Actually, i have also noticed this.
It implies that an exploit might not succeed (this usually the case
with most exploits), since the attacker supplied shellcode will not be
at the "expected" location.
My question is, does anybody know why this happens? Why this
difference when running qemu with
25 matches
Mail list logo
