search for: ndomain

Hi, This patch removes the magic number "31" for readability. The number "31" means the idle domain ID. In detail: - display the idle domain ID with "Idle" instead of "31" - write to the file "log-idle.log" instead of "log-dom31.log". Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> Thanks, -- KUWAMURA

Is there (if not, can we get) the functionality to query for workstations in the local workgroup or domain? Zach

Dear Andrew Tridgell I have a small Problem. At the moment I am using Samba_2.0.7, and I must say this is a very good product, but until now there is a limitation. The User on the Windows and Unix Machine must always be the same. I think this was so or I have overseen some fundamental configuring steps. But thats obsolete with Samba_2.2. Now I plan to test and eventually upgrade to Samba_2.2. I

...armhf&ver=4.17.3%2B10-g091466ba55-1.1&stamp=1709892742&raw=0 xenstored_control.c:646:70: error: format ?%ld? expects argument of type ?long int?, but argument 5 has type ?time_t? {aka ?long long int?} [-Werror=format=] 646 | ret = talloc_asprintf(ctx, "%s\nDomain %u: %ld s", | ~~^ | | | long int |...

...- info = dev->archdata.iommu; - if (info && info != DUMMY_DEVICE_DOMAIN_INFO && info != DEFER_DEVICE_DOMAIN_INFO) - return (info->domain == si_domain); - - return 0; -} - static int domain_add_dev_info(struct dmar_domain *domain, struct device *dev) { struct dmar_domain *ndomain; @@ -3461,12 +3450,6 @@ static struct dmar_domain *get_private_domain_for_dev(struct device *dev) return domain; } -/* Check if the dev needs to go through non-identity map and unmap process.*/ -static bool iommu_no_mapping(struct device *dev) -{ - return iommu_dummy(dev) || identity_mapping(d...

...---- - Start xenmon by simply running xenmon.py; The xenbake demon is started and stopped automatically by xenmon. - To see the various options for xenmon, run xenmon -h. Ditto for xenbaked. - xenmon also has an option (-n) to output log data to a file instead of the curses interface. - NDOMAINS is defined to be 32, but can be changed by recompiling xenbaked - Xenmon.py appears to create 1-2% cpu overhead; Part of this is just the overhead of the python interpreter. Part of it may be the number of trace records being generated. The number of trace records generated can be limite...

I am rebasing Fedora rawhide oprofile package to oprofile-0.9.7. The xenoprof patches on http://xenoprof.sourceforge.net/#download look a bit dated. The newest version is for oprofile-0.9.5. I massaged the patch oprofile-0.9.5-xen.patch to apply to oprofile-.0.9.7. Attached is that updated patch. Does this look reasonable? Is there a desire to get this into upstream oprofile? Or should the

From: Zhang Xiantao <xiantao.zhang@intel.com> With virtual EPT support, L1 hyerpvisor can use EPT hardware for L2 guest''s memory virtualization. In this way, L2 guest''s performance can be improved sharply. According to our testing, some benchmarks can show > 5x performance gain. Signed-off-by: Zhang Xiantao <xiantao.zhang@intel.com> Zhang Xiantao (11):

...mu) */ iommu->domain_ids = kcalloc(nlongs, sizeof(unsigned long), GFP_KERNEL); if (!iommu->domain_ids) { - printk(KERN_ERR "Allocating domain id array failed\n"); + pr_err("Allocating domain id array failed\n"); return -ENOMEM; } iommu->domains = kcalloc(ndomains, sizeof(struct dmar_domain *), GFP_KERNEL); if (!iommu->domains) { - printk(KERN_ERR "Allocating domain array failed\n"); + pr_err("Allocating domain array failed\n"); return -ENOMEM; } @@ -1325,7 +1323,7 @@ static int iommu_attach_domain(struct dmar_domain *d...

...mu) */ iommu->domain_ids = kcalloc(nlongs, sizeof(unsigned long), GFP_KERNEL); if (!iommu->domain_ids) { - printk(KERN_ERR "Allocating domain id array failed\n"); + pr_err("Allocating domain id array failed\n"); return -ENOMEM; } iommu->domains = kcalloc(ndomains, sizeof(struct dmar_domain *), GFP_KERNEL); if (!iommu->domains) { - printk(KERN_ERR "Allocating domain array failed\n"); + pr_err("Allocating domain array failed\n"); return -ENOMEM; } @@ -1325,7 +1323,7 @@ static int iommu_attach_domain(struct dmar_domain *d...

...mu) */ iommu->domain_ids = kcalloc(nlongs, sizeof(unsigned long), GFP_KERNEL); if (!iommu->domain_ids) { - printk(KERN_ERR "Allocating domain id array failed\n"); + pr_err("Allocating domain id array failed\n"); return -ENOMEM; } iommu->domains = kcalloc(ndomains, sizeof(struct dmar_domain *), GFP_KERNEL); if (!iommu->domains) { - printk(KERN_ERR "Allocating domain array failed\n"); + pr_err("Allocating domain array failed\n"); return -ENOMEM; } @@ -1325,7 +1323,7 @@ static int iommu_attach_domain(struct dmar_domain *d...

This patchset converts the intel iommu driver to the dma-iommu api. While converting the driver I exposed a bug in the intel i915 driver which causes a huge amount of artifacts on the screen of my laptop. You can see a picture of it here: https://github.com/pippy360/kernelPatches/blob/master/IMG_20191219_225922.jpg This issue is most likely in the i915 driver and is most likely caused by the

This patchset converts the intel iommu driver to the dma-iommu api. While converting the driver I exposed a bug in the intel i915 driver which causes a huge amount of artifacts on the screen of my laptop. You can see a picture of it here: https://github.com/pippy360/kernelPatches/blob/master/IMG_20191219_225922.jpg This issue is most likely in the i915 driver and is most likely caused by the