ransaction instead of two 32bit
memory transaction
On 09/02/2011 12:46 AM, Adnan Khaleel wrote:
> Is there anyway we can prevent Qemu breaking up 64,128 and 256bit XMM or
YMM instructions into smaller chunks and have them issue as a single
transaction of the original width?
Not
te: Tue, 9 Nov 2010 17:57:28 +
> Legacy. Patches have been submitted to add 64 bit IO handlers. But > there
> have been other discussions to change the whole I/O interface.
> On Mon, Nov 8, 2010 at 11:27 PM, Adnan Khaleel wrote:>> In
> the file exec.c:
&g
PCI express support has been made available for quite sometime now with patches
from Isaku Yamahata for the Q35 chipset for Qemu 0.12 and then for Qemu 0.14.
However, Qemu 0.15 has been released but support for the Q35 chipset is still
not officially included.
At what point will Qemu merge the
I'm using Qemu along with a network simulator and I need to perform a
synchronization every N cycles. What is the best way to do this in Qemu so that
I can call a function periodically say every N instructions or simulated cpu
cycles?
Currently I have a routine in main_loop() in vl.c but it see
I'm using Isaku Yamahata's q35 chipset model in Qemu0.14 and I'm trying to
figure out why the Qemu dhcpd server is not responding back to the nic device
in the guest OS when used with user mode networking.
The guest OS sees the network device and initialises it but I think the Qemu
DHCP server/f
I finally got this work after I realised that the AHCI driver was not being
loaded in my disk image and that ACHI was not being enabled in the Seabios
.config file.
This is really good work Yamahata, thanks.
As far as I can tell, everything works like the stock Qemu 0.14 except
networking. The
lyadi.sant...@gmail.com]
To: ad...@khaleel.us
Cc: qemu-devel@nongnu.org
Sent: Tue, 10 May 2011 01:49:31 -0500
Subject: Re: [Qemu-devel] Howto debug boot device not showing up in bios
Hi
On Tue, May 10, 2011 at 05:24, Adnan Khaleel wrote:
> Can somebody give me some pointers on what th
partition cannot be seen and I get a
message saying
"Waiting for device /dev/disk/by-uuid/ to appear: Could not
find /dev/disk/by-uuid/"
Any ideas whats happening here?
AK
_
From: Adnan Khaleel [mailto:ad...@khaleel.us]
To: ad...@khaleel.us
Cc: Hu Tao
Can somebody give me some pointers on what the best way to debug the boot
process in Qemu and seabios?
Seabios reports that no boot device is present even though I'm passing it the
hda commandline argument.
What I'm looking for in particular is what Qemu does to map the path to a
device and h
Yes, it was a git version conflict. Thanks.
Adnan
_
From: Isaku Yamahata [mailto:yamah...@valinux.co.jp]
To: Adnan Khaleel [mailto:ad...@khaleel.us]
Cc: Hu Tao [mailto:hu...@cn.fujitsu.com], qemu-devel@nongnu.org
Sent: Thu, 21 Apr 2011 11:38:36 -0500
Subject: Re: [Qemu-devel] [PATCH 00
/MergeSpace/qemu_0.14_q35/qemu/.git/clone-tmp':
Directory not empty
_
From: Isaku Yamahata [mailto:yamah...@valinux.co.jp]
To: Adnan Khaleel [mailto:ad...@khaleel.us]
Cc: Hu Tao [mailto:hu...@cn.fujitsu.com], qemu-devel@nongnu.org
Sent: Wed, 20 Apr 2011 21:07:46 -0500
Subject: Re: [Qemu-
/qemu_0.14_q35/qemu/.git/clone-tmp':
Directory not empty
Adnan
_
From: Isaku Yamahata [mailto:yamah...@valinux.co.jp]
To: Hu Tao [mailto:hu...@cn.fujitsu.com], Adnan Khaleel
[mailto:ad...@khaleel.us]
Cc: qemu-devel@nongnu.org
Sent: Wed, 20 Apr 2011 17:46:44 -0500
Subject: Re: [Qemu-devel] [
In trying out various simulated memory sized in Qemu, there is a noticeable
increase in guest bootup times with more memory. My metric of measuring how
long linux takes to boot is probably not the most consistent but here is what
I've observed.
In Qemu 0.12.5
512m ~ 4 mins
2048m ~ 7 mins
I
were offsets
so I'm inclined to believe that the address is an offset from the start of the
BAR. So let me ask my question again - when I'm synthesizing the PCIe
transaction to send to the PCIe device model, do I have to give it a full
address i.e. bus,dev,fn for config transactions
Hello,
I have a question regarding how Qemu PCIe devices handle Config Transactions vs
Memory Transactions (assuming the PCI device is setup to act as
PCI_BASE_ADDRESS_SPACE_MEMORY).
I'm using portions of hw/cirrus_vga.c to make my point,
static PCIDeviceInfo cirrus_vga_info = {
.qdev
In the file exec.c:
The memory Write/Read functions are declared as an array of 4 entries where the
index values of 0,1,2 correspond to 8,16 and 32bit write and read functions
respectively.
CPUWriteMemoryFunc *io_mem_write[IO_MEM_NB_ENTRIES][4];
CPUReadMemoryFunc *io_mem_read[IO_MEM_NB_ENTRIES]
Are all these patches going to be integrated into the current qemu repository?
-AK
_
From: Isaku Yamahata [mailto:yamah...@valinux.co.jp]
To: Michael S. Tsirkin [mailto:m...@redhat.com]
Cc: qemu-devel@nongnu.org, skand...@cisco.com, etmar...@cisco.com,
we...@cisco.com, ad...@khaleel.us
S
During bootup, I also see the following error message:
pci :40:00.0: BAR 0 bad alignment 20:
0x00-0x1f
Any idea whats causing this?
AK
_
From: Isaku Yamahata [mailto:yamah...@valinux.co.jp]
To: Adnan Khaleel [mailto:ad...@khaleel.us]
Cc: Cam
I've tried everything you mentioned and I still get the same problem. The only
thing that seems to avoid that issue is if I reduce the aperture size from
0x20ull to 0x200ull.
Here is the relevant section of code:
static const unsigned long long BAR_Regions[6][2] =
{
// len , ty
0;
}
Thanks
AK
_
From: Cam Macdonell [mailto:c...@cs.ualberta.ca]
To: ad...@khaleel.us
Cc: Isaku Yamahata [mailto:yamah...@valinux.co.jp], qemu-devel@nongnu.org
Sent: Fri, 27 Aug 2010 10:48:48 -0500
Subject: Re: [Qemu-devel] Template for developing a Qemu device with PCIe and
MSI-X
O
Hi there. I should have sent a lot of these with my note yesterday but I was in
a hurry to get the files to you first.
See my comments below and thanks again.
AK
pcie_msix_write_config() should call pci_default_write_config()
unless you did it so intentionally.I've made this change. Than
m interested in.
Is the overall architecture of any qemu device still similar to how a typical
qemu pci device is or is there anything I should be aware of?
Thanks again Isaku.
AK
_
From: Isaku Yamahata [mailto:yamah...@valinux.co.jp]
To: Adnan Khaleel [mailto:ad...@khaleel.us]
Cc: q
tried a simple helloworld program
and even that seems to be taking forever to compile. Not sure if there is
something wrong with my bcc install.
AK
_
From: Isaku Yamahata [mailto:yamah...@valinux.co.jp]
To: Adnan Khaleel [mailto:ad...@khaleel.us]
Cc: qemu-devel@nongnu.org
Sent: Fri, 20 Au
? I'm compiling from a
typical bash shell and using gcc v4.4.0.
In vgabios, there is a requirement for bcc. Is that borland C compiler?
Thanks
Adnan
_
From: Isaku Yamahata [mailto:yamah...@valinux.co.jp]
To: Adnan Khaleel [mailto:ad...@khaleel.us]
Cc: qemu-devel@nongnu.org
Sent: W
Hi Isaku, thank you very much for your very detailed response. I have a few
questions, see below.
Thanks again,
Adnan
Qemu doesn't support pcie at the moment.
Only partial patches have been merged, still more patches have to
be merged for pcie to fully work. The following repo is availabl
Hello Qemu developers,
I'm interested in developing a device model that plugs into Qemu that is based
on a PCIe interface and uses MSI-X. My goal is to ultimately attach a GPU
simulator to this PCIe interface and use the entire platfom (Qemu + GPU
simulator) for studying cpu, gpu interactions.
uld happen anytime soon.
From: David S. Ahern [mailto:daah...@cisco.com]
To: ad...@khaleel.us
Cc: Qemu-devel@nongnu.org
Sent: Fri, 21 May 2010 13:47:00 -0500
Subject: Re: [Qemu-devel] Problems changing dvdrom iso during
execution
On 05/21/2010 10:10 AM, Adnan Khaleel wrote:
> So do you have a
ytime soon.
_
From: David S. Ahern [mailto:daah...@cisco.com]
To: ad...@khaleel.us
Cc: Qemu-devel@nongnu.org
Sent: Fri, 21 May 2010 13:47:00 -0500
Subject: Re: [Qemu-devel] Problems changing dvdrom iso during execution
On 05/21/2010 10:10 AM, Adnan Khaleel wrote:
> So do you have any idea
dvdrom iso during execution
On 05/20/2010 03:48 PM, Adnan Khaleel wrote:
> Thanks for your response.
>
>
> Does it work if the guest uses ide based CD's:
> rmmod ide-scsi
> modprobe ide-cd
>
> There isn't an ide-scsi but the
Thanks for your response.
Does it work if the guest uses ide based CD's:
rmmod ide-scsi
modprobe ide-cd
There isn't an ide-scsi but there is a scsi_mod and when I try to remove that
it gives
ERROR: Module scsi_mod is in use by sr_mod,sg,sd_mod,libata
modprobe ide-cd seems to work.
I cannot change DVD roms during execution using the monitor. I can only mount a
cdrom/dvdrom if I specify the iso file in the command line
x86_64-softmmu/qemu-system-x86_64 -hda ../../OSImages/sles11.qcow2 -cdrom
../../ISOz/mydvd.iso -m 2048
In the guest I can mount the iso image as you could n
Could one of the developers give a brief status of the current state of support
for PCIe and MSI-X interrupts in Qemu.
I'm trying to build a System-C device that I'd like to co-simulate with Qemu
and have the ability to use the same software stack as well. The kernel modules
rely on MSI-X interr
Hi there,
I'm using qemu-0.7.1 to install SUSE Linux enterprise v9 and everything
proceeds smoothly until the boot loader as to be installed as which point I get
the SUSE installer reporting a "segmentation fault while installing GRUB".
The hard disk image is in raw format I created using qemu-i
33 matches
Mail list logo
