search for: devcie

I have been trying to write my own user defined function in Rpart.I imitated the anova splitting rule which is given as an example.In the work I am doing ,I am calculating the concentration index(ci) ,which is in between -1 and +1.So my deviance is given by abs(ci)*(1-abs(ci)).Now when I run rpart incorporating this user defined function i get the following error message: Error in

Current index allocation in virtio is based on a monotonically increasing variable "index". This means we'll run out of numbers after a while. E.g. someone crazy doing this in host side. while(1) { hot-plug a virtio device hot-unplug the virito devcie } Signed-off-by: Asias He <asias at redhat.com> --- drivers/virtio/virtio.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/drivers/virtio/virtio.c b/drivers/virtio/virtio.c index 984c501..f355807 100644 --- a/drivers/virtio/virtio.c +++ b/drivers/virtio/vi...

Current index allocation in virtio is based on a monotonically increasing variable "index". This means we'll run out of numbers after a while. E.g. someone crazy doing this in host side. while(1) { hot-plug a virtio device hot-unplug the virito devcie } Signed-off-by: Asias He <asias at redhat.com> --- drivers/virtio/virtio.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/drivers/virtio/virtio.c b/drivers/virtio/virtio.c index 984c501..f355807 100644 --- a/drivers/virtio/virtio.c +++ b/drivers/virtio/vi...

From: Sui Jingfeng <suijingfeng at loongson.cn> Patch 1,2 and 3 do basic clean up to the vgaarb module. Patch 4 introduce is_boot_device function callback to vga_client_register Sui Jingfeng (4): PCI/VGA: tidy up the code and comment format PCI/VGA: Use unsigned type for the io_state variable PCI/VGA: only deal with VGA class devices PCI/VGA: introduce is_boot_device function

Recently our automated testing system has caught a curious assertion while testing Xen 4.1.5 on a HaswellDT system. (XEN) Assertion ''(sp == 0) || (peoi[sp-1].vector < vector)'' failed at irq.c:1030 (XEN) ----[ Xen-4.1.5 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e008:[<ffff82c48016b2b4>] do_IRQ+0x514/0x750 (XEN) RFLAGS: 0000000000010093 CONTEXT:

...ne VIRTIO_CRYPTO_S_STARTED (1 << 1) + +struct virtio_crypto_config { + /* See VIRTIO_CRYPTO_OP_* above */ + __virtio32 status; + + /* + * Maximum number of data queue legal values are between 1 and 0x8000 + */ + __virtio32 max_dataqueues; + + /* + * Specifies the services mask which the devcie support, + * see VIRTIO_CRYPTO_SERVICE_* above + */ + __virtio32 crypto_services; + + /* Detailed algorithms mask */ + __virtio32 cipher_algo_l; + __virtio32 cipher_algo_h; + __virtio32 hash_algo; + __virtio32 mac_algo_l; + __virtio32 mac_algo_h; + __virtio32 aead_algo; + /* Maximum length of cip...

...ne VIRTIO_CRYPTO_S_STARTED (1 << 1) + +struct virtio_crypto_config { + /* See VIRTIO_CRYPTO_OP_* above */ + __virtio32 status; + + /* + * Maximum number of data queue legal values are between 1 and 0x8000 + */ + __virtio32 max_dataqueues; + + /* + * Specifies the services mask which the devcie support, + * see VIRTIO_CRYPTO_SERVICE_* above + */ + __virtio32 crypto_services; + + /* Detailed algorithms mask */ + __virtio32 cipher_algo_l; + __virtio32 cipher_algo_h; + __virtio32 hash_algo; + __virtio32 mac_algo_l; + __virtio32 mac_algo_h; + __virtio32 aead_algo; + /* Maximum length of cip...

...+#define VIRTIO_CRYPTO_S_HW_READY (1 << 0) + +struct virtio_crypto_config { + /* See VIRTIO_CRYPTO_OP_* above */ + __le32 status; + + /* + * Maximum number of data queue legal values are between 1 and 0x8000 + */ + __le32 max_dataqueues; + + /* + * Specifies the services mask which the devcie support, + * see VIRTIO_CRYPTO_SERVICE_* above + */ + __le32 crypto_services; + + /* Detailed algorithms mask */ + __le32 cipher_algo_l; + __le32 cipher_algo_h; + __le32 hash_algo; + __le32 mac_algo_l; + __le32 mac_algo_h; + __le32 aead_algo; + /* Maximum length of cipher key */ + __le32 max_ciph...

...+/* The accelerator hardware is ready */ +#define VIRTIO_CRYPTO_S_HW_READY (1 << 0) + +struct virtio_crypto_config { + /* See VIRTIO_CRYPTO_OP_* above */ + __u32 status; + + /* + * Maximum number of data queue + */ + __u32 max_dataqueues; + + /* + * Specifies the services mask which the devcie support, + * see VIRTIO_CRYPTO_SERVICE_* above + */ + __u32 crypto_services; + + /* Detailed algorithms mask */ + __u32 cipher_algo_l; + __u32 cipher_algo_h; + __u32 hash_algo; + __u32 mac_algo_l; + __u32 mac_algo_h; + __u32 aead_algo; + /* Maximum length of cipher key */ + __u32 max_cipher_key_l...

...PTO_S_HW_READY (1 << 0) > + > +struct virtio_crypto_config { > + /* See VIRTIO_CRYPTO_OP_* above */ > + __u32 status; > + > + /* > + * Maximum number of data queue > + */ > + __u32 max_dataqueues; > + > + /* > + * Specifies the services mask which the devcie support, > + * see VIRTIO_CRYPTO_SERVICE_* above > + */ > + __u32 crypto_services; > + > + /* Detailed algorithms mask */ > + __u32 cipher_algo_l; > + __u32 cipher_algo_h; > + __u32 hash_algo; > + __u32 mac_algo_l; > + __u32 mac_algo_h; > + __u32 aead_algo; > +...

...PTO_S_HW_READY (1 << 0) > + > +struct virtio_crypto_config { > + /* See VIRTIO_CRYPTO_OP_* above */ > + __u32 status; > + > + /* > + * Maximum number of data queue > + */ > + __u32 max_dataqueues; > + > + /* > + * Specifies the services mask which the devcie support, > + * see VIRTIO_CRYPTO_SERVICE_* above > + */ > + __u32 crypto_services; > + > + /* Detailed algorithms mask */ > + __u32 cipher_algo_l; > + __u32 cipher_algo_h; > + __u32 hash_algo; > + __u32 mac_algo_l; > + __u32 mac_algo_h; > + __u32 aead_algo; > +...

v3: - set cpu affinity when data queues are not equal to the number of online cpus. [Michael] - add TODO comments for cpu hotplug (changing the relationship of binding virtqueue and cpu) - use __u32/64 in the config space since the virtio->get() doesn't support byte-swap yet. [Michael] - drop the whole patch 1 of v2 because the above reason. - add VERSION_1 check at the beginning of

v3: - set cpu affinity when data queues are not equal to the number of online cpus. [Michael] - add TODO comments for cpu hotplug (changing the relationship of binding virtqueue and cpu) - use __u32/64 in the config space since the virtio->get() doesn't support byte-swap yet. [Michael] - drop the whole patch 1 of v2 because the above reason. - add VERSION_1 check at the beginning of

...virtio_crypto_config { > > + /* See VIRTIO_CRYPTO_OP_* above */ > > + __u32 status; > > + > > + /* > > + * Maximum number of data queue > > + */ > > + __u32 max_dataqueues; > > + > > + /* > > + * Specifies the services mask which the devcie support, > > + * see VIRTIO_CRYPTO_SERVICE_* above > > + */ > > + __u32 crypto_services; > > + > > + /* Detailed algorithms mask */ > > + __u32 cipher_algo_l; > > + __u32 cipher_algo_h; > > + __u32 hash_algo; > > + __u32 mac_algo_l; > >...

The virtio crypto device is a virtual cryptography device as well as a kind of virtual hardware accelerator for virtual machines. The encryption anddecryption requests are placed in the data queue and are ultimately handled by thebackend crypto accelerators. The second queue is the control queue used to create or destroy sessions for symmetric algorithms and will control some advanced features in

The virtio crypto device is a virtual cryptography device as well as a kind of virtual hardware accelerator for virtual machines. The encryption anddecryption requests are placed in the data queue and are ultimately handled by thebackend crypto accelerators. The second queue is the control queue used to create or destroy sessions for symmetric algorithms and will control some advanced features in

...t; +struct virtio_crypto_config { > + /* See VIRTIO_CRYPTO_OP_* above */ > + __le32 status; > + > + /* > + * Maximum number of data queue legal values are between 1 and 0x8000 > + */ > + __le32 max_dataqueues; > + > + /* > + * Specifies the services mask which the devcie support, > + * see VIRTIO_CRYPTO_SERVICE_* above > + */ > + __le32 crypto_services; > + > + /* Detailed algorithms mask */ > + __le32 cipher_algo_l; > + __le32 cipher_algo_h; > + __le32 hash_algo; > + __le32 mac_algo_l; > + __le32 mac_algo_h; > + __le32 aead_algo;...

...t; +struct virtio_crypto_config { > + /* See VIRTIO_CRYPTO_OP_* above */ > + __le32 status; > + > + /* > + * Maximum number of data queue legal values are between 1 and 0x8000 > + */ > + __le32 max_dataqueues; > + > + /* > + * Specifies the services mask which the devcie support, > + * see VIRTIO_CRYPTO_SERVICE_* above > + */ > + __le32 crypto_services; > + > + /* Detailed algorithms mask */ > + __le32 cipher_algo_l; > + __le32 cipher_algo_h; > + __le32 hash_algo; > + __le32 mac_algo_l; > + __le32 mac_algo_h; > + __le32 aead_algo;...