From: Anh Nguyen <nguyenminhanh@gmail.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: a xen question
Date: Fri, 7 May 2010 14:14:38 -0700 [thread overview]
Message-ID: <s2tf90f1ab01005071414id7e52322y23717a576cc0755b@mail.gmail.com> (raw)
In-Reply-To: <i2vf90f1ab01005071413nd1cc16bcp22f13fa154517440@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 4108 bytes --]
Sorry. The table format was lost in the previous email.
Audio
ES1370 emulation es1370.c
Soundblaster 16 emulation sb16.c
Graphic
VGA Emulator vga*
Cirrus CLGD 54xx VGA Emulator cirrus_vga.c
Xen Console xen_console.c
QEMU VNC display driver ..\vnc.c
Net
e1000 Ethernet emulation e1000*
NE2000 emulation ne2000.c
QEMU RTL8139 emulation rtl8139.c
Other
PC System Emulator pc.c, ..\vl.c
PCI pci*
PCI MSI support pt-msi.c
QEMU PC keyboard emulation pckbd.c
QEMU VMMouse emulation vmmouse.c
PS/2 Port ps2*
QEMU MC146818 RTC emulation mc146818rtc.c
usb usb*, ..\usb*
Battery Management battery_mgmt*
DMA emulation dma.c, ..\dma*
Floppy disk emulator (Intel 82078) fdc*
QEMU IDE disk and CD/DVD-ROM Emulator ide.c, cdrom.c
LSI53C895A SCSI Host Bus Adapter emulation lsi53c895a.c
ACPI & PIIX acpi, piix*
QEMU 8253/8254 interval timer emulation i8254.c
QEMU 8259 interrupt controller emulation i8259.c
QEMU Parallel PORT emulation parallel.c
PC speaker emulation pcspk.c
APIC apic.c
ISA Bus isa*
16550A UART emulation serial.c
SCSI Device emulation scsi*
TPM tpm*
High Precisition Event Timer emulation hpet*
QEMU I2C bus interface i2c*
SMBus device emulation smbus*
Virtio Devices virtio*
VMPort emulation vmport.c
XEN event channel device xen_platform*
Xen paravirt framebuffer xenfb*, ..\xenfbfront.c
XenStore ..\xenstore.c
-Anh
On Fri, May 7, 2010 at 2:13 PM, Anh Nguyen <nguyenminhanh@gmail.com> wrote:
> Thanks Stefano,
>
> I looked into the code and this is what I got. Does this look right to you?
>
> Audio ES1370 emulation es1370.c Soundblaster 16 emulation sb16.c Graphic
> VGA Emulator vga* Cirrus CLGD 54xx VGA Emulator cirrus_vga.c Xen Console
> xen_console.c QEMU VNC display driver ..\vnc.c Net e1000 Ethernet
> emulation e1000* NE2000 emulation ne2000.c QEMU RTL8139 emulation
> rtl8139.c PC System Emulator pc.c, ..\vl.c PCI pci* PCI MSI support
> pt-msi.c QEMU PC keyboard emulation pckbd.c QEMU VMMouse emulation
> vmmouse.c PS/2 Port ps2* QEMU MC146818 RTC emulation mc146818rtc.c usb
> usb*, ..\usb* Battery Management battery_mgmt* DMA emulation dma.c, ..\dma*
> Floppy disk emulator (Intel 82078) fdc* QEMU IDE disk and CD/DVD-ROM
> Emulator ide.c, cdrom.c LSI53C895A SCSI Host Bus Adapter emulation
> lsi53c895a.c ACPI & PIIX acpi, piix* QEMU 8253/8254 interval timer
> emulation i8254.c QEMU 8259 interrupt controller emulation i8259.c QEMU
> Parallel PORT emulation parallel.c PC speaker emulation pcspk.c APIC
> apic.c ISA Bus isa* 16550A UART emulation serial.c SCSI Device emulation
> scsi* TPM tpm* High Precisition Event Timer emulation hpet* QEMU I2C bus
> interface i2c* SMBus device emulation smbus* Virtio Devices virtio* VMPort
> emulation vmport.c XEN event channel device xen_platform* Xen paravirt
> framebuffer xenfb*, ..\xenfbfront.c XenStore ..\xenstore.c
>
> Best,
>
>
>
> On Fri, May 7, 2010 at 3:56 AM, Stefano Stabellini <
> stefano.stabellini@eu.citrix.com> wrote:
>
>> On Thu, 6 May 2010, George Dunlap wrote:
>> > Ahn, the backends and frontends depends on which version of the kernel
>> > you're using. Do you want to look at the pv-ops kernel (the long-term
>> > future), or the xen-linux kernel (a fork which will never make it
>> > as-is into Linux, but is ATM more widely used)?
>> >
>> > Stefano, which devices are enabled in qemu in our Xen tree? Can you
>> > give Anh some pointers on how to find out which files correspond to
>> > those devices? Thanks!
>> >
>>
>>
>> Just starting a Linux HVM guest and executing lspci in the guest is a
>> good start :)
>>
>> The entry to point to start all the emulated devices in qemu is
>> pc_init1 in hw/pc.c, from there you can find out all the
>> initialization functions of the emulated hardware provided by qemu to
>> the guest.
>> The main ones are the graphic card (two models available:
>> hw/cirrus_vga.c and hw/vga.c), network cards (two models available:
>> hw/e1000.c, hw/rtl8139.c), PIIX4 (hw/piix4acpi.c), PIIX3 (hw/piix_pci.c,
>> hw/ide.c, hw/usb-uhci.c), usb devices (hw/usb-hid.c), the xen pci
>> platofirm device (hw/xen_platform.c) and the serial card (hw/serial.c).
>>
>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 11467 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-05-07 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BDCC4EC.5070704@uiuc.edu>
[not found] ` <i2mf90f1ab01005012247kef06f908jbda998be2eb071c8@mail.gmail.com>
2010-05-06 20:36 ` a xen question George Dunlap
2010-05-06 20:45 ` Anh Nguyen
2010-05-07 10:56 ` Stefano Stabellini
2010-05-07 21:13 ` Anh Nguyen
2010-05-07 21:14 ` Anh Nguyen [this message]
2010-05-10 9:20 ` Stefano Stabellini
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=s2tf90f1ab01005071414id7e52322y23717a576cc0755b@mail.gmail.com \
--to=nguyenminhanh@gmail.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.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).